Even for prefetching this seem rather worthless as it won't allow prefetching start significantly earlier over the resources specified in the document source. There is also (based on the experience in similar things) a high chance that whatever is listed in the Link header won't match what the document actually uses and so will end up slowing down the page load. antti 2010/11/9 Gavin Peters (蓋文彼德斯) <gavinp@chromium.org>:
Firefox supports it for rel=prefetch, and it was my thought to include that support in my patch. That use is worthwhile: it allows server specification of prefetch resources, as opposed to author (as in HTML).l - Gavin
On 9 November 2010 12:20, Maciej Stachowiak <mjs@apple.com> wrote:
On Nov 9, 2010, at 9:00 AM, Alexey Proskuryakov wrote:
09.11.2010, в 03:51, Alex Milowski написал(а):
Now that RFC 5988 is a proposed standard [1] and HTML5 references the "Link:" header [2]
Note the way in which HTML5 references it: "Some versions of HTTP defined a Link: header". That's about HTTP 1.0 only.
Specifying stylesheets in HTTP headers seems like a most obvious misfeature to me, and other potential uses of the Link header field are so unimportant that RFC 5988 doesn't even bother to mention them in its introduction.
It might be worth testing which other browsers support it. I know at least Firefox supports associating a stylesheet with Link. It does seem like a fairly ill-conceived feature, but not so much that it is worth being the sole holdout, if other browser engines all do it. And there are some plausible use cases - same document served with multiple stylesheets, without having to modify the document on the fly, just the headers.
Regards, Maciej
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev