RESOLVED FIXED 61079
Add rel type prerender to distinguish prerender from prefetch
https://bugs.webkit.org/show_bug.cgi?id=61079
Summary Add rel type prerender to distinguish prerender from prefetch
Gavin Peters
Reported 2011-05-18 10:57:22 PDT
Add rel type prerender to distinguish prerender from prefetch
Attachments
Patch (18.49 KB, patch)
2011-05-18 11:48 PDT, Gavin Peters
no flags
Patch (18.47 KB, patch)
2011-05-18 12:06 PDT, Gavin Peters
no flags
Patch (18.56 KB, patch)
2011-05-18 12:33 PDT, Gavin Peters
no flags
Gavin Peters
Comment 1 2011-05-18 11:48:57 PDT
Gavin Peters
Comment 2 2011-05-18 11:50:01 PDT
Also, see how I cleaned things up in CachedResourceRequest.cpp? I like the new cachedResourceTypeToTargetType a lot better.
WebKit Review Bot
Comment 3 2011-05-18 11:52:22 PDT
Attachment 93958 [details] did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files', u'LayoutTests/ChangeLog', u'LayoutTests/fast..." exit_code: 1 Source/WebCore/loader/cache/CachedResourceLoader.h:73: The parameter name "priority" adds no information, so it should be removed. [readability/parameter_name] [5] Total errors found: 1 in 16 files If any of these errors are false positives, please file a bug against check-webkit-style.
Gavin Peters
Comment 4 2011-05-18 11:54:43 PDT
Unfortunately, this has tickled me before, the style failure doesn't recognise a default parameter as sufficient reason to name an argument.
Gavin Peters
Comment 5 2011-05-18 11:56:41 PDT
Comment on attachment 93958 [details] Patch bad patch. new upload pending.
Gavin Peters
Comment 6 2011-05-18 12:06:01 PDT
Gavin Peters
Comment 7 2011-05-18 12:06:41 PDT
Comment on attachment 93961 [details] Patch Better patch. Thank you dominich@chromium.org.
WebKit Review Bot
Comment 8 2011-05-18 12:07:55 PDT
Attachment 93961 [details] did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files', u'LayoutTests/ChangeLog', u'LayoutTests/fast..." exit_code: 1 Source/WebCore/loader/cache/CachedResourceLoader.h:73: The parameter name "priority" adds no information, so it should be removed. [readability/parameter_name] [5] Total errors found: 1 in 16 files If any of these errors are false positives, please file a bug against check-webkit-style.
Early Warning System Bot
Comment 9 2011-05-18 12:30:07 PDT
Gavin Peters
Comment 10 2011-05-18 12:33:45 PDT
Gavin Peters
Comment 11 2011-05-18 12:34:03 PDT
Comment on attachment 93966 [details] Patch Fix non-prefetching builds!
WebKit Review Bot
Comment 12 2011-05-18 12:36:22 PDT
Attachment 93966 [details] did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files', u'LayoutTests/ChangeLog', u'LayoutTests/fast..." exit_code: 1 Source/WebCore/loader/cache/CachedResourceLoader.h:73: The parameter name "priority" adds no information, so it should be removed. [readability/parameter_name] [5] Total errors found: 1 in 16 files If any of these errors are false positives, please file a bug against check-webkit-style.
Adam Barth
Comment 13 2011-05-20 15:27:06 PDT
Comment on attachment 93966 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=93966&action=review > Source/WebCore/html/HTMLLinkElement.cpp:263 > priority = ResourceLoadPriorityLow; We don't want to set priority = ResourceLoadPriorityLow for prerender as well?
Gavin Peters
Comment 14 2011-05-21 07:32:45 PDT
Comment on attachment 93966 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=93966&action=review >> Source/WebCore/html/HTMLLinkElement.cpp:263 >> priority = ResourceLoadPriorityLow; > > We don't want to set priority = ResourceLoadPriorityLow for prerender as well? I think no; the VeryLow that it gets by default is probably correct. Priority in WebKit loading only controls when requests are sent to the network layer (the lower the priority, the later they go out), and for prerender being late like a prefetch is probably correct; the prerender fetch then won't interfere as much with main resource loading. In the subresource case, the contrast is that the resource is associated with the current page, and Low priority mirrors what something like an image would get.
WebKit Commit Bot
Comment 15 2011-05-21 12:23:33 PDT
The commit-queue encountered the following flaky tests while processing attachment 93966 [details]: http/tests/websocket/tests/handshake-fail-by-cross-origin.html bug 54147 (author: abarth@webkit.org) The commit-queue is continuing to process your patch.
WebKit Commit Bot
Comment 16 2011-05-21 12:25:07 PDT
Comment on attachment 93966 [details] Patch Clearing flags on attachment: 93966 Committed r87020: <http://trac.webkit.org/changeset/87020>
WebKit Commit Bot
Comment 17 2011-05-21 12:25:14 PDT
All reviewed patches have been landed. Closing bug.
WebKit Commit Bot
Comment 18 2011-05-21 13:25:28 PDT
The commit-queue encountered the following flaky tests while processing attachment 93966 [details]: http/tests/websocket/tests/close-event.html bug 61240 (author: yutak@chromium.org) The commit-queue is continuing to process your patch.
Gavin Peters
Comment 19 2011-05-23 12:27:40 PDT
I have learned a valuable lesson; always test the chrome side of a webkit patch that has chrome implication before uploading to WebKit: https://bugs.webkit.org/show_bug.cgi?id=61297 catches two mistakes that shouldn't have been in this bug.
Note You need to log in before you can comment on or make changes to this bug.