#282: TextEncoderStream and TextDecoderStream
Discussions
2018-11-28
Alex: argument is that pieces are welded shut because that's a good thing. i'd like to see the data. I'll respond
Kenneth: [related to]... transform streams?
Alex: it's all very wired shut
Kenneth: the transport stream is more like an interface.
Alex: it's not clear that you'll get the same behavior - generating new streams out of existing streams... what s is the delegation mechanism...
Yves: what is the default encoding of streams in javascript?
Alex: ...
Alex: you can't just make a transform stream...
[...discussion on what feedback to leave...]
Alex: https://streams.spec.whatwg.org/#is-transform-stream
David: if there are issues with transform streams it's worth raising them.
Alex: i'd like to make this less magic. Will leave feedback
2018-12-04
Kenneth: Looking at issues around typing and TransformStreams.
Sangwhan: some people have issues with UTF-8 being the only encoding.
Yves: last telcon, we discussed the fact that natively js is ucs2 not utf8 - so the current name might be misleading
Kenneth: up-to-date example code?
Alex: no constructor so can't subclass?
Kenneth: domenic says you can
Alex: still an issue with subclassability - have followed up on the issue
2019-01-08
Kenneth: alex's comment about subclassing / not subclassing. They say you should subclass...
Alex: I'll provide feedback today
2019-01-22
Peter: currently pending external feedback.
Travis: Have an outstanding 'subclassing' issue. Should probably wait to the F2F.
OpenedMay 22, 2018
Hello TAG!
I'm requesting a TAG review of:
Further details (optional):
You should also know that...
This is an extension to the existing Encoding Standard to integrate with the Streams Standard. There has been extensive discussion at https://github.com/whatwg/encoding/issues/72.
We'd prefer the TAG provide feedback as (please select one):