[whatwg/fetch] Should `processResponse` also receive the internal response, similar to `processResponseConsumeBody`? (Issue #1664)

Commit 900326635be4509de38f1a61084565731ac115c4 changed the fetch response handover steps to provide `processResponseConsumeBody` with the response's internal response. Should the invocation to `processResponse` just before also receive the internal response?

This was an issue for us over at [SerenityOS](https://github.com/SerenityOS/serenity) when implementing the HTMLMediaElement, for example. When we fetch the media resource, [the spec says](https://html.spec.whatwg.org/multipage/media.html#loading-the-media-resource:concept-fetch) to use the `processResponse` algorithm to incrementally read the response's body. However, all CORS cross-origin (i.e. filtered) responses will have a null body at this step.

Or maybe the HTML spec should say to incrementally read the body of the response's unsafe response?

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

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