Re: [whatwg/fetch] How should the ReadableStream from response.body work when it's multipart? (#1021)

I think this is reasonably established at this point: the bytes of the `ReadableStream` should be the raw bytes on the wire that represent the formdata request. This is also visible by just doing:

```js
const fd = new FormData();
const resp = new Response(fd);
for await (const chunk of resp.body) {
  console.log("chunk", chunk);
}
```

@domenic: I was unable to reproduce the issue you mentioned in my own testing. Chrome can "collect" multipart formdata responses just fine: https://dash.deno.com/playground/formdata-test. I think there was an issue with your test setup. I think we even have WPTs for this to some extent (`fetch/api/response/response-init-002.any.js tests the serialization).

As such I think we can close the issue? A streaming `FormData` reader seems like a separate issue (something I'd like to tackle in the future though).

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

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