Re: [whatwg/fetch] Take tainted origin flag into account for the same origin check (#834)

My thinking was that for `<img>` A -> B -> A (without CORS) results in a "same origin" image that can be read through `<canvas>`. HTML would have to poke through the opaque response filter Fetch adds to enable that. (However, given https://github.com/whatwg/fetch/issues/737#issuecomment-439592046 we might be able to change things around here if we wanted.)

-- 
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/834#issuecomment-439837919