Disambiguate fetch-request-streams feature #3361
Conversation
github-actions
bot
added
the
feature definition
|
Based on web-platform-tests/interop#1072 (comment) another option here is to just move |
Rewrite the fetch-request-streams feature to make it more clear what precise property it covers, and add a new fetch-body-stream feature to cover the `body` option to the `fetch` function supporting `ReadableStream` objects.
jgraham
force-pushed
the
fetch_streams
branch
from
12778fd to
7ffcd14
Compare
|
OK, I've updated this to just make the more minimal change of requiring that the I'm not delighted with that, because it obscures the fact that part of the feature is already available in Safari, but it's better than the status quo. |
| @@ -1,5 +1,6 @@ | |||
| name: Fetch upload streams | |||
| description: A `fetch()` request uploads a stream of data to the server when a request's `body` property is a `ReadableStream` object. | |||
| name: Request body property | |||
There was a problem hiding this comment.
The only thing I'm not 100% sure about is the name. Isn't it a problem that we're loosing the "stream" part of it?
According to MDN, the body part of a request can either be null or a stream.
So, really, it's only used for streaming requests to a server, right?
What other things can it be used for?
Rewrite the fetch-request-streams feature to make it more clear what precise property it covers, and add a new fetch-body-stream feature to cover the
bodyoption to thefetchfunction supportingReadableStreamobjects.