Contact emailsnidh...@chromium.org, ri...@chromium.org, yhi...@chromium.org
The streams APIs provide ubiquitous, interoperable primitives for creating, composing, and consuming streams of data. This change permits an underlying sink to rapidly abort an ongoing write or close when requested by the writer.
Previously, when writer.abort() was called, a long-running write would still have to continue to completion before the stream could be aborted. With this change, the write can be aborted immediately.
TAG reviewNot needed as this is an incremental improvement to an existing feature.
TAG review statusNot applicable
Interoperability and Compatibility
Low risk because streams has already been standardised for a long time (since around 2014). Other browsers have implemented other parts of the standard, and they will most likely also adapt this feature as well soon.Gecko
: Positive (https://github.com/whatwg/streams/pull/1132#issuecomment-867114529
) Mozilla is supportive of Streams but has not yet shipped WritableStream. It is expected that they will include this feature when they do. They have also expressed interest in implementing WebTransport, and therefore are supportive of this feature.WebKit
: No signalWeb developers
: No signals
A lot of design efforts have been made into making the streams API easy to use. Additionally, this feature is only a small change to the existing streams API that developers are used to.
An underlying sink which doesn't observe the controller.signal will continue to have the existing behavior.
No special support needed.Yes
Requires code in //chrome?False
Link to entry on the Chrome Platform Statushttps://chromestatus.com/feature/5698931422920704This intent message was generated by Chrome Platform Status.