|Summary:||Remove UTF-7 and UTF-32 support|
|Product:||WebKit||Reporter:||Anne van Kesteren <annevk>|
|Severity:||Normal||CC:||ap, cdumez, eoconnor, jshin, masa141421356, mjs, Ms2ger, syoichi|
|Version:||528+ (Nightly build)|
Description Anne van Kesteren 2011-12-15 08:34:25 PST
I'm not sure what the right component is or who to copy on this bug exactly, but per HTML UTF-7 and UTF-32 should not be supported. Gecko and Presto have disabled these already. WebKit/Chromium would preferably follow us here.
Comment 1 Alexey Proskuryakov 2011-12-15 13:47:38 PST
Do you have a test case for out UTF-7 support? That would be a bug, as we were supposed to have blocked it long ago, <http://trac.webkit.org/changeset/49487>. What is the rationale to ban UTF-32?
Comment 2 Theresa O'Connor 2011-12-15 13:53:22 PST
ap: from the HTML spec ( http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html#character-encodings-0 ): Support for UTF-32 is not recommended. This encoding is rarely used, and frequently implemented incorrectly. This specification does not make any attempt to support EBCDIC-based encodings and UTF-32 in its algorithms; support and use of these encodings can thus lead to unexpected behavior in implementations of this specification.
Comment 3 Alexey Proskuryakov 2011-12-15 14:04:11 PST
So, the rationale is "rarely used, and frequently implemented incorrectly".