- From: Andrew Betts <notifications@github.com>
- Date: Sat, 07 Apr 2018 03:53:18 +0000 (UTC)
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 7 April 2018 03:54:20 UTC
TAG has been discussing the scope and nomenclature around this. I am wondering whether you considered creating an additional directive, to indicate that preload should additionally explore the dependency graph of the resource, in a similar vein to the `includeSubdomains` directive of `Strict-Transport-Security`. This would allow this 'deep-preload' behaviour to be tied specifically to certain media types. We note that the `as` attribute of `Link` is a [destination as specified in fetch](https://fetch.spec.whatwg.org/#concept-request-destination), and a subset of these values represent media types that potentially have a dependency graph (specifically document, script, style and serviceworker). Example: ``` Link: </path/to/something>; rel=preload; as=script; includeDependencies <link rel="preload" href="/path/to/something" as="script" includeDependencies> ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/213#issuecomment-379429902
Received on Saturday, 7 April 2018 03:54:20 UTC