Re: [whatwg/fetch] Should request's origin be exposed to javascript (#272)

> Thinking about this more I think exposing it on the ForeignFetchEvent rather than just the Request would be really weird, as you could just call new ForeignFetchEvent({request: r}).origin anyway to get the origin out of any arbitrary request. So having the getter on the event wouldn't actually change the requests for which the origin would be exposed, it just slightly obscures it for some.

I think this depends on when the origin is set, no?  The ForeignFetchEvent.origin could be set during dispatch.

I continue to dislike putting mutable state on Request, but I'll concede if you all want it there.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/272#issuecomment-218856068