- From: Anne van Kesteren <notifications@github.com>
- Date: Mon, 08 Apr 2019 09:56:02 -0700
- To: whatwg/encoding <encoding@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 8 April 2019 16:56:24 UTC
I think I'm convinced that adding this to `String` in some manner is the way to go if it's needed. Encodings require UTF strings as input and only output UTF strings. And `TextEncoder` isn't the only API that has such a requirement and acts in this "lossy" way. Every API that uses `USVString` does this, so we'd need a generic solution, which makes this an input problem, not a specific API problem. -- 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/issues/174#issuecomment-480913868
Received on Monday, 8 April 2019 16:56:24 UTC