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

@samuelgoto commented on this pull request.



> @@ -1796,13 +1798,27 @@ to not have to set <a for=/>request</a>'s <a for=request>referrer</a>.
   <dt>"<code>navigate</code>"
   <dd>This is a special mode used only when <a>navigating</a> between documents.
 
+  <dt>"<code>unsafe-no-cors</code>"

> One point against "unsafe" here might be that it's not useful to web developers as this value is also exposed to them. From that perspective "user-agent-no-cors" is prolly better.

Just to double check: do I understand it correctly that this is also going to be exposed to web developers (as `Sec-Fetch-Mode=unsafe-no-cors`), in addition to browser engineers? 

If so, the name shouldn't trigger suspicion by the web developer (who should trust that the spec was written in a careful and thoughtful way, rather than something that the developer has to re-check again), right?

>  From that perspective "user-agent-no-cors" is prolly better.

Right. `user-agent-no-cors` would make it do and I think would also address @jyasskin 's point (and @annevk 's, to trigger spec reviewers to look carefully).

FWIW, `mediated-no-cors` could work too for me, just as a suggestion (`user-agent-no-cors` works too I think).

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

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