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

Well, `<img>` can already be explained in terms of Fetch (#concept-fetch, to be precise). Nothing extra is needed for that. #48 is about a developer-facing API. And bypassing `connect-src` is okay, as long as you can guarantee the response is bound to the context, which we can (at least theoretically).

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