Adam Rice
Adam Rice
@isonmad submitted a pull request #601 to support asymmetric default->byte TransformStream objects. Although only default->default and default->byte transforms are possible at the moment, I expect that byte->default and byte->byte will...
From a usability perspective, a blocking API is very attractive. However, the impact on interactivity would be unacceptable on the main thread. An interesting possibility is to provide a blocking...
The explainer contains the same example that @jeremyroman fixed in the specification. Apply the same fixes there.
There should be a way to register algorithms that are not built-in but can be used to construct CompressionStream and DecompressionStreams in the same realm. @domenic provided the following API...
The "deflate" format supports preset dictionaries. These permit backreferences to be used from the start of the data to refer to items in the dictionary as if it was prepended...
It would be good to explicitly match the format names in https://www.iana.org/assignments/http-parameters/http-parameters.xhtml#content-coding. Currently we implicitly match them, so it's not a big change. It's unclear what to do about possible...
Maybe we should have something like ```idl static Promise compress(DOMString format, BufferSource input); ``` in CompressionStream, and a similar API for DecompressionStream, to make one-shot compression and decompression easier to...
`CompressionStream.prototype.format` should be a getter which returns the format the stream was created with. Similarly `DecompressionStream.prototype.format`.
I would like to extract the WebSocket sections from the HTML and Fetch standards and combine them into a single standard. My major motivation for this is to create a...
https://streams.spec.whatwg.org/commit-snapshots/eb1769cd4654d3e494ddc7a4e1d3001eb77641d7/#ref-for-chunk⑦⑧ > Let result be the result of running cancelAlgorithm The _reason_ is not passed to _cancelAlgorithm_. Originally reported at https://github.com/w3c/webtransport/issues/412.