- From: Timothy Gu <notifications@github.com>
- Date: Thu, 12 Jul 2018 20:58:54 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/fetch/issues/777/404718824@github.com>
(For those who don't want to read IRC logs, all of this is observable through the `Referer` header and using the `fetch()` function from an `iframe` for example.) We probably don't want to use the word "invoking" here at all, since it can mean multiple things: the ES Call abstract operation; [invoke](https://heycam.github.io/webidl/#invoke-a-callback-function) a callback function algorithm (this is probably the closest, since it contains logic to convert IDL arguments to back ES, even though `Request` is not a callback function in the IDL sense); or just "execute the steps listed for that constructor"? > I think we want it to be the relevant realm of this WindowOrWorkerGlobalScope object. This would cause a slight discrepancy between `fetch()` and `Request()`. The [`Request()` constructor](https://fetch.spec.whatwg.org/#dom-request) explicitly uses the [current settings object](https://html.spec.whatwg.org/multipage/webappapis.html#current-settings-object) as the client of the new request it's creating; i.e., the realm for which the `Request` function was created. I think we would want more testing before deciding if we want to use the relevant realm or the current realm. -- 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/777#issuecomment-404718824
Received on Friday, 13 July 2018 03:59:18 UTC