Intent to Ship: textStream() for response/request/blob

[Chromestatus]

Contact emails

nrose...@chromium.org

Explainer

https://github.com/whatwg/fetch/pull/1862

Specification

https://github.com/whatwg/fetch/pull/1862

Summary

Add textStream() to interfaces that represent a byte stream (request, response, blob). This is equivalent to piping the byte stream through a TextDecoderStream(), and reduces this small piece of broilerplate for commoncases.

Blink component

Blink>Network>FetchAPI

Web Feature ID

Missing feature

Motivation

A small ergonomic change to make it easier to stream text from a byte stream such as response (or blob) to a sink that accepts strings. Helps with a footgun of forgetting to pipe through a TextDecoderStream.

Initial public proposal

https://github.com/whatwg/fetch/pull/1862

TAG review

No information provided

TAG review status

Not applicable

Goals for experimentation

None

Risks

Interoperability and Compatibility

No information provided

Gecko: No signal

WebKit: Positive (https://github.com/whatwg/fetch/pull/1862#issuecomment-4622913023) (too small for an official standards position)

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

No information provided

Debuggability

No information provided

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?

Yes

Is this feature fully tested by web-platform-tests?

Yes
See https://github.com/web-platform-tests/wpt/pull/60356

Flag name on about://flags

No information provided

Finch feature name

TextStreamMethod

Rollout plan

Will ship enabled for all users

Requires code in //chrome?

False

Tracking bug

https://issues.chromium.org/issues/514448226

Estimated milestones

Shipping on desktop	151
Shipping on Android	151
Shipping on WebView	151

Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).

No information provided

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5146752165478400?gate=6123591876870144

Links to previous Intent discussions

Intent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a0c802d.2b0a0220.109f42.0022.GAE%40google.com

This intent message was generated by Chrome Platform Status.