Re: [whatwg/fetch] processResponseConsumeBody and opaque responses (Issue #1446)

If the HTML/CSS specs need to support no-cors fetches, then they also need access to the response body... 
As long as the bytes are not exposed directly to the web developer, I don't see what's missing and how another warning would add to the current documentation of what opaque responses are about...

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1446#issuecomment-1142503549
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1446/1142503549@github.com>

Received on Tuesday, 31 May 2022 18:26:33 UTC