Re: [fetch] Initializing context/content specific fetch defaults (#43)

> Enforce CSP based on specified context? /cc @mikewest

Having `as` set context makes sense, but wouldn't that prevent authors from specifying various priorities to the fetched resource? e.g. If I have a background image that's extremely important and I want it to download in the same priority as CSS, I won't have a way to communicate that to the browser. IIRC that use case is the main reason the attribute is called `as` rather than `context`.

If we go that route then maybe, for the case of `<link rel=preload>`, we need to add some priority hints on top of the context.



---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/43#issuecomment-93650410