Re: [fetch] Introduce convenience property for request's context (#93)

> For this both the .isNavigation = true and the .context = "document" proposals would work, right? And how we would treat workers wouldn't affect this use case?

If I knew the request was going to create a document or child-document client, I wouldn't need `.isNavigation`.

> (influencing Accept) would seem like an argument for treating workers as script, and for treating all image types as a single type

Agreed. We may want to expose a more detailed initiator in future, but it seems simpler as a starting point to go with what CSP and ServiceWorker already define.

> Does any of the proposals made so far help with (priority)?

It depends how fine-grained prioritisation needs to be. Do browsers treat `<img>` and background images differently priority-wise? Prioritisation is unspecced, but the browser can attach whatever private data to a request object, once that's used in a call to `fetch(req)` the browser can use that priority.

> Is the proposal that the service worker would somehow take over the responsibility of enforcing CSP?

Nah, I'm only talking about CSP to show that the idea is building upon what's already specced elsewhere, whereas a granular "initiator" would be a new and big thing.

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