- From: Henri Sivonen <notifications@github.com>
- Date: Tue, 02 Apr 2019 22:06:13 -0700
- To: whatwg/encoding <encoding@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 3 April 2019 05:06:35 UTC
> I'm somewhat worried that the reason is that exactly that alternative is not exposed in the API and developers are not aware that it's currently lossy by default. I'm not saying that it's unimportant, because the Web Platform doesn't have at already. I'm saying that Firefox is a large codebase that deals with UTF-16 and UTF-8 and gets away with not having it internally. It's not conclusive, but it's a data point. > (I personally wasn't aware of this until running into this issue.) The input event issue is a problem, but I think one problem shouldn't be extrapolated into an assumption that it's going to be a common case. -- 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-479341376
Received on Wednesday, 3 April 2019 05:06:35 UTC