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

Thanks @ehsan. That matches my thoughts almost exactly. I'm not sure if there's value in the second or third bullet. But adding properties for those seems like it can be done as use-cases come up.

The other thing to keep in mind that when "what is being loaded" is "a document" then we don't actually know that the resource will be a HTML document. A URL being loaded into a top-level window or into an <iframe> can be at least a HTML/XML/SVG document, an image, a audio file, a video file, a plugin, or a pdf. Or probably a bunch of other things. This is fine, but just something we should keep in mind to either clearly document, or to make it clear when naming the enum-value for navigation.

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