whatwg/streams Issues

Last updated Nov 21, 2024, 6:00:43 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

Untriaged

Try to triage issues within . [ More Info ]

Issue Title Within SLO On maintainers' plates for Time left Time past SLO
#384 TransformStream should allow transform algorithm to function as pull source ❌
#659 Tests for optimised implementations of piping ❌
#742 Make sure ReadableByteStream's respond() works for all with/without (BYOB)Reader ❌
#825 Use [[UpperCamelCase]] in internal slots ❌
#905 pipeTo says "in parallel", but that isn't really right ❌
#942 Participation agreement requirement non-obvious ❌
#1001 DetachArrayBuffer can throw ❌
#1016 Provide a way to communicate the current optimal write size ❌
#1031 WebSocket example bug & questions ❌
#1086 Using streams from other specs: explain some best practices for byte streams ❌
#1156 Allow web authors to tee() with cloned chunks ❌
#1222 How to create a transformed WritableStream that waits for close? ❌
#1233 Clarify: tee is unsafe for independent consumption since it backpressures to the faster consumer ❌
#1254 Add maxByteLength option to "read all bytes" algo ❌
#1260 Why resolve backpressurePromise by an error message in SetUpCrossRealmTransformWritable? ❌
#1290 Consider making writer.abort() automatically generate an "AbortError" DOMException? ❌
#1299 read all bytes: Why only Uint8Array instead of general BufferSource? ❌
#1326 Commit pull-into descriptors after filling from queue ❌
#1331 Abort followed by write on WritableStream may invoke a null strategy algorithm ❌