Re: [fetch] Handling of data URLs (#111)

Okay. So if mode is "no-cors" you can end up with an opaque response that is a data URL. The idea behind this was e.g., `<img>` setting this flag and displaying the data URL either way, but it was wrapped in an opaque response you would not be able to paint it on `<canvas>` and then export the `<canvas>` data.

Similar with `fetch()`. You can read a data URL normally, but if it's the result of a redirect you only have an opaque response which you can perhaps give to something that can display it down the road, but you won't be able to do much else with it.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/111#issuecomment-132157118