Re: [whatwg/encoding] Add TextEncoderStream and TextDecoderStream transform streams (#149)

> If we find compelling use cases for easily reading legacy content we may need to support it in future, but my personal preference would be to leave it out until it is proven necessary.
...
> The semantics are strictly greedy. Given the same chunks as input, every browser is required to have exactly the same chunk boundaries in the output.

OK. Thanks.

-- 
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/149#issuecomment-412101256

Received on Friday, 10 August 2018 14:35:37 UTC