12011-05-18 Gavin Peters <gavinp@chromium.org>
2
3 Reviewed by NOBODY (OOPS!).
4
5 Add rel type prerender to distinguish prerender from prefetch
6 https://bugs.webkit.org/show_bug.cgi?id=61079
7
8 Chrome right now uses <link rel=prefetch ...> for one of two things,
9 to warm the cache in the same way as firefox, or to launch a speculative
10 rendering of a web page, for faster "loading" when the user navigates to it.
11
12 This new rel type will let us distinguish the two cases; the rel type prerender
13 isn't used on the web today, but the Google Web Search example prerendering application
14 is ready to experiment with it.
15
16 Test: fast/dom/HTMLLinkElement/prerender.html
17
18 * html/HTMLLinkElement.cpp:
19 (WebCore::HTMLLinkElement::tokenizeRelAttribute):
20 (WebCore::HTMLLinkElement::process):
21 * html/HTMLLinkElement.h:
22 (WebCore::HTMLLinkElement::RelAttribute::RelAttribute):
23 * loader/cache/CachedResource.cpp:
24 (WebCore::defaultPriorityForResourceType):
25 * loader/cache/CachedResource.h:
26 (WebCore::CachedResource::isLinkResource):
27 * loader/cache/CachedResourceLoader.cpp:
28 (WebCore::createResource):
29 (WebCore::CachedResourceLoader::requestLinkResource):
30 (WebCore::CachedResourceLoader::canRequest):
31 * loader/cache/CachedResourceLoader.h:
32 * loader/cache/CachedResourceRequest.cpp:
33 (WebCore::cachedResourceTypeToTargetType):
34 (WebCore::CachedResourceRequest::load):
35 * platform/network/ResourceRequestBase.h:
36