Re: [whatwg/fetch] fetch() "no-cors": cross-origin to same-origin redirect taints response (#737)

Interesting; Chrome is indeed one of the violators of not resetting tainting back to "basic" after a `fetch()` lands on same-origin after cross-origin redirect, but this is a simple change. Are you considering a spec change here depending on what implementations are doing?

-- 
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/737#issuecomment-392309163