Re: [whatwg/fetch] CORB: nosniff handling (#686)

Those error messages though only reach the console, they are not exposed to web content, so I don't think we need to care for them here.

As for "opaque-filtered response", part of the point there is that some features, e.g., `<img>` will dig into the underlying response to get out the bits and display an image. CORB should prevent that for certain responses so I think you want to filter all of "no-cors"...

-- 
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/686#issuecomment-383829600