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

So it seems we need quite a few things to replace context and context frame type:

* request's type (image, scripts, video, etc.)
* request's result type (document, worker, sharedworker, resource etc.)
* request's browsing context ancestor origins (for offline UI)
* request's initiator (form, picture, img; for CSP and Mixed Content)

Of those we would expose the first three to service workers. Does this make sense? Should I try to work this out?

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