Re: [whatwg/fetch] Add unsafe-no-cors mode (PR #1533)

> > I was operating under the assumption that the client would either be a cloned ESO or null, with the necessary other arguments specified, which is already in the spec as a possible argument.
> 
> When you say "which is already in the spec as a possible argument," do you mean that we expect all `unsafe-no-cors` consumers to explicitly specify `request.policy container` and `request.referrer policy` etc., and so on, for all of the request members that would otherwise be derived implicitly from `client` (which I guess is null for these kinds of requests)?

I meant that this spec already supports a `null` client, so I assumed this wasn't breaking new ground. If `request.client` is null, I expect that consumers would have to explicitly specify all arguments that default to `"client"`.

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

Message ID: <whatwg/fetch/pull/1533/c1424595762@github.com>