Re: [fetch] Mechanism to indicate "destination context" (#64)

When I talked with @sicking about this he also immediately suggested context as the way to go. Using a MIME type as a way to set a longer `Accept` header seems very flawed and not exposing a primitive that UAs currently have or would likely have.

> [D]ifference between "navigate to next" and "used by current page" is already captured via the source context (i.e. prefetch vs preload)

Are "fetch" and "load" really the right words in that case? They don't really convey that difference. Either makes sense in the context of the current environment, especially now we have `fetch()`.

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