[Bug 27435] Document.inputEncoding

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27435

--- Comment #12 from Boris Zbarsky <bzbarsky@mit.edu> ---
In Gecko the canonical encoding name for UTF-8 is "UTF-8".

The canonical encoding name for windows-1252 is "windows-1252".

It sounds like Blink does the same.

What do other UAs do?

Seems to me like ideally the canonical names in the encoding standard would
match UA behavior to the extent it's interoperable.

inputEncoding should just return the canonical name, imo.  We shouldn't be
adding stupid complexity and special casing here if we can avoid it.

Fwiw, what TextEncoder/TextDecoder do in Gecko is to just always lowercase our
internal canonical name before returning.  :(

> Having to guess the case of the encoding name is no fun.

I agree, but neither is breaking compat.  :(

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 27 November 2014 14:38:11 UTC