Re: [whatwg/encoding] Amount of bytes to sniff for encoding detection (#102)

> encoding labels goes against https://encoding.spec.whatwg.org/ and therefore also against HTML. It's not clear to me what of that ends up being exposed to Chrome though, maybe it's not?

The encoding name strings in CED aren't web-exposed in Chrome.  They didn't become valid meta tag encoding names or anything.

> Does that also mean we'd never detect ISO-2022-JP or UTF-16, which are ASCII-incompatible?

We are currently detecting ISO-2022-JP and UTF-16.  We'll make another triage pass and come up with a minimal whitelist of necessary ones (which almost certainly shouldn't contain UTF-16 at least).

> It's still unclear to me what motivated the CED detector as other browsers don't have a similar complex thing.

What motivated it is that the encoding selection menu other browsers have isn't a workable solution on phones where UI space is limited.  Also, Firefox, IE and older versions of Chrome do have autodetectors, they're just not enabled by default.

-- 
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/102#issuecomment-303262934