Re: [whatwg/encoding] Allow conformant implementations to support non-UTF-8 encodings (#144)

> The suggestion that huge parts of the web, which were created (in "good faith") using non-UTF-8 charset encoding, and continue to be created that way, should be made non-browsable so as to make browser behavior uniform, seems bizarre and, frankly, somewhat offensive.

I think there's a misunderstanding. The Encoding Standard both defines non-UTF-8 encodings and requires them to be supported. So such legacy content will continue to function just fine.

> And that's doubly the case considering how additional charset encodings are to be added in the future anyway.

What makes you say this?

It'd greatly help if you could separate your concerns clearly, as the API is really somewhat separate from all this and has its own design considerations.

-- 
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/144#issuecomment-390464426