[whatwg/encoding] Fix TextDecoderStream's behavior when processing the end of stream (#265)

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.

Fixes #263.

<!--
Thank you for contributing to the Encoding Standard! Please describe the change you are making and complete the checklist below if your change is not editorial.
-->

- [X] At least two implementers are interested (and none opposed):
   * Firefox and Safari implement this.
   * Chrome has bugs around end-of-stream handling, but they are shared with `TextDecoder`'s non-streaming mode.
- [ ] [Tests](https://github.com/web-platform-tests/wpt) are written and can be reviewed and commented upon at:
   * …
- [ ] [Implementation bugs](https://github.com/whatwg/meta/blob/main/MAINTAINERS.md#handling-pull-requests) are filed:
   * Chrome: https://bugs.chromium.org/p/chromium/issues/detail?id=978522

   * Firefox: N/A
   * Safari: N/A

(See [WHATWG Working Mode: Changes](https://whatwg.org/working-mode#changes) for more details.)

You can view, comment on, or merge this pull request online at:

  https://github.com/whatwg/encoding/pull/265


-- Commit Summary --

  * Fix TextDecoderStream's behavior when processing the end of stream

-- File Changes --

    M encoding.bs (36)

-- Patch Links --

https://github.com/whatwg/encoding/pull/265.patch

https://github.com/whatwg/encoding/pull/265.diff


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/pull/265