Remove UTF-7 and UTF-32 support 
https://bugs.webkit.org/show_bug.cgi?id=74610
Summary Remove UTF-7 and UTF-32 support
Anne van Kesteren
Reported 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.
Attachments
Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 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?
Theresa O'Connor
Comment 2 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.
Alexey Proskuryakov
Comment 3 2011-12-15 14:04:11 PST
So, the rationale is "rarely used, and frequently implemented incorrectly".
Masahiro Yamada
Comment 4 2013-03-06 07:45:19 PST
Support of UTF-7 is removed by bug 29078. But other unrecommended encoding are still supported. (CESU-8, UTF-7, BOCU-1 and SCSU) Matrix of supported encoding names per browser is here: http://l0.cm/encodings/table/
Anne van Kesteren
Comment 5 2023-05-29 02:18:23 PDT
What is UTF7Encoding() about? Is that for WebKit embedders? If so, I suspect this is fixed as UTF-7 is blocklisted somewhere.
Note You need to log in before you can comment on or make changes to this bug.