-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use readable byte stream for Blob.stream() and Response.body #17386
Comments
We actually already use readable byte streams for both of these APIs which seem to align with behaviour in the spec PRs, so will close this |
Oh, interesting! In that case are you interested to how to spec the behavior? whatwg/fetch#1593 (comment) |
BTW, |
|
actually, apparently i missed the fact that there was a recent-ish change #16038 that might have changed our behaviour. |
seems like Response constructor with either string or typedarray has a different path, and is creating the stream differently: Lines 95 to 100 in 10e4b2e
looks like a trivial change |
|
|
Corresponds to whatwg/fetch#1593 and w3c/FileAPI#188.
The text was updated successfully, but these errors were encountered: