- From: Mike West <notifications@github.com>
- Date: Tue, 22 Oct 2019 06:27:03 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 22 October 2019 13:27:05 UTC
I think my original proposal was `no-cors` for everything. `navigate` for everything seems reasonable once we're in a world where plugins aren't a problem. `no-cors` seems reasonable for requests whose response might end up in a plugin depending on type. I don't think it makes a huge difference either way, as @arturjanc and team would just need to look at the destination in addition to the mode for navigation requests, which they already need to do for `iframe` and `frame`. That said, less well-informed developers might be inclined to treat `navigate` as totally fine. Better documentation and example code might help mitigate that risk? I can live with either, I think. -- 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/pull/948#issuecomment-544961142
Received on Tuesday, 22 October 2019 13:27:05 UTC