Name already in use

See https://github.com/whatwg/spec-factory for details.

See tc39/proposal-shadowrealm#331 for context.

See https://github.com/whatwg/spec-factory for details.

This change fixes TextDecoderStream's "flush and enqueue" algorithm to handle the end of the stream in the same way as a call to TextDecoder's decode() method with no parameters.

Tests: web-platform-tests/wpt#29481.

Fixes #263.

At various times in the ISO-2022-JP decoder and encoder, the prepend operation was being called with an end-of-queue item, even though that was made illegal in #215. This change removes those instances, in order to keep the same behavior as before #215.

Follows whatwg/streams#1110.

See https://github.com/whatwg/spec-factory for details.

Closes #253.

Helps with whatwg/meta#174.

"Run" is now "process a queue" and "process" is now "process an item".

Also tidy up the error mode note and shorten the "process an item" algorithm.

Closes #245.

Closes #239 and closes #243.

And also stop defaulting error mode in "run" and "process".

Fixes #240.

Since the ISO-2022-JP encoder is stateful (no other encoding is) the existing hooks were not adequately supporting the needs of URL percent-encoding which needs to handle output bytes differently from errors.

Fixes #235.

And make some small editorial changes to the "run" and "process" algorithms.

This avoids the need for "prepend" in the "process" algorithm as is needed to fix #235. 

Additionally, this commit adds two clarifying asserts to the "process" algorithm documenting what error modes can be in effect when.

Related tests: web-platform-tests/wpt#26158.

An "output" parameter was added to the hooks for standards in #215, but no explanation was given as to why it was needed. This change adds that clarification.

Follows whatwg/streams#1073.

Co-authored-by: Andreu Botella <[email protected]>
Co-authored-by: Anne van Kesteren <[email protected]>

This change renames the Encoding-specific concept of "streams", which
had been causing confusion with readable/writable streams for years, to
"I/O queues". It also refactors the I/O queue operations and exports the
corresponding definitions.

As part of this refactoring, "end-of-queue" (formerly "end-of-stream")
becomes an optional item in the queue, indicating that the end of the
streaming data has been reached and that no more data is expected. As a
result, the "read" operation explicitly blocks when trying to read from
an empty queue – a behavior that was previously left unstated.

Closes #180.

See https://github.com/whatwg/spec-factory for details.

See https://github.com/whatwg/spec-factory for details.

This was left over from #175.