- From: <bizzbyster@gmail.com>
- Date: Wed, 30 Jul 2014 13:07:40 -0500
- To: Ilya Grigorik <igrigorik@google.com>
- Cc: public-web-perf <public-web-perf@w3.org>
Received on Wednesday, 30 July 2014 18:08:08 UTC
Thanks. I'll follow the discussion on that thread. Peter On Jul 30, 2014, at 1:01 PM, Ilya Grigorik <igrigorik@google.com> wrote: > > On Wed, Jul 30, 2014 at 10:49 AM, <bizzbyster@gmail.com> wrote: > The use of the attribute "context" in the LINK element is confusing to me. Your doc includes a reference to the FETCH spec (http://fetch.spec.whatwg.org) for a definition of context. But then in that table it says the context of a LINK rel=subresource should be "sub resource". > > WIP... it's not clear to me that subresource/prefetch (currently specced context's) should be there: > https://github.com/igrigorik/resource-hints/issues/6#issuecomment-50368295 > > Also, in your resource-hints doc, you indicate that context is mainly provided for priority. But do we also want to use it to provide a way to set the Accept header values in the preloaded request? > > It should work as expected... e.g. context=image would advertise correct accept headers sent by the UA for image requests, and so on. > > ig
Received on Wednesday, 30 July 2014 18:08:08 UTC