Re: [whatwg/fetch] Same-origin data-URL flag only for fetch and XHR? (#381)

> the specification is largely aligned with Chrome already.

I was being flippant. By "the spec", I was talking more about HTML "origin of a document" than Fetch.

> The problem here is that Chrome is not consistent.

Yup. I said "ideally" because I agree with you that Chrome's current behavior is weird in some places. I suspect that `data:` images in `<canvas>` is the only exception that's probably baked in for web compatibility purposes. I don't have much data to back that up, of course.

@tyoshino might know more about Chrome's CORS exceptions for `data:` in general, as he's been working in that code more recently.

-- 
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/381#issuecomment-245199391