Intent to Implement: TextEncoderStream and TextDecoderStream APIs

[Adam Rice]

Contact emails ri...@chromium.org, yhi...@chromium.org Spec

Explainer: https://github.com/ricea/encoding-streams/blob/master/stream-explainer.md.

Extensive discussion has taken place on the Encoding Standard repository: https://github.com/whatwg/encoding/issues/72

TAG review: https://github.com/w3ctag/design-reviews/issues/282 Summary Integration of the Encoding Standard with the Stream Standard. This enables developers to easily convert streams of binary data to text and vice-versa. This is generally useful when working with streams of text, and fills a vital need when used with the Fetch API. Motivation Without these objects developers will be forced to roll their own. See the explainer for why this is problematic. Interoperability risk Firefox: No public signals Edge: No public signals Safari: No public signals Web developers: No signals

Two new constructors will be added to the global object. This has been the conclusion of discussions on the Encoding Standard repository and has rough consensus from the participants there. The behaviour of the new objects is based on elements of the Encoding Standard and Stream Standard that are already stable, and so changes are unlikely to be required.

Compatibility risk Very low. I am not aware of any existing use of these names in Javascript. Ongoing technical constraints None. Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? Yes or no. Yes. OWP launch tracking bug https://bugs.chromium.org/p/chromium/issues/detail?id=845427 Link to entry on the Chrome Platform Status https://www.chromestatus.com/features/4881011259211776 Requesting approval to ship? No.

[Yoav Weiss]

Happy to see this being worked on. This is a long-awaited feature, and can enable data reduction in multiple scenarios.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAC_ixdx5m4gY61XXOvwDwvpxdHAXSCmznSe63PMPe2KhPHUrWA%40mail.gmail.com.

[Harald Alvestrand]

Sad to see the word "stream" used in yet another incompatible meaning, but the functionality seems extremely useful!

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAC_ixdx5m4gY61XXOvwDwvpxdHAXSCmznSe63PMPe2KhPHUrWA%40mail.gmail.com.

--

You received this message because you are subscribed to the Google Groups "blink-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEgAyng3uMYH9oWTvUc8wbxh0MFzqkTXbX9dtNrQt-VYdg%40mail.gmail.com.

[Anne van Kesteren]

On Thu, May 24, 2018 at 3:23 PM, 'Harald Alvestrand' via blink-dev
<blin...@chromium.org> wrote:
> Sad to see the word "stream" used in yet another incompatible meaning, but
> the functionality seems extremely useful!

Context?


--
https://annevankesteren.nl/

[Harald Alvestrand]

From explainer:

Non-goals

• Unification of WHATWG Streams with the concept of a stream used in the Encoding Standard. Despite having the same name, they are different in functionality and purpose. Since the Encoding Standard's "stream" concept is just an internal piece of spec terminology, this has no impact on developers.
  

It's actually not clear from the explainer that the streams in this specification refer to WHATWG Streams. Adding a sentence saying that somewhere close to this paragraph would make it (even more) obvious.

[Adam Rice]

Unification of WHATWG Streams with the concept of a stream used in the Encoding Standard. Despite having the same name, they are different in functionality and purpose. Since the Encoding Standard's "stream" concept is just an internal piece of spec terminology, this has no impact on developers.

We did discuss renaming the Encoding Standard's concept of a stream to something like "token sequence" to avoid this ambiguity, but it felt like a distraction from the more important work that needed doing.

It's actually not clear from the explainer that the streams in this specification refer to WHATWG Streams. Adding a sentence saying that somewhere close to this paragraph would make it (even more) obvious.

Thanks for the feedback. I will try to make it clearer.