74610 2011-12-15 08:34:25 -0800 Remove UTF-7 and UTF-32 support 2023-05-29 02:18:23 -0700 1 1 1 Unclassified WebKit Platform 528+ (Nightly build) Unspecified Unspecified NEW https://bugs.webkit.org/show_bug.cgi?id=159651 https://bugs.webkit.org/show_bug.cgi?id=10709 P2 Normal --- 1 annevk webkit-unassigned ap cdumez eoconnor jshin masa141421356 mjs Ms2ger syoichi oldest_to_newest 521918 0 annevk 2011-12-15 08:34:25 -0800 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. 522217 1 ap 2011-12-15 13:47:38 -0800 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? 522218 2 eoconnor 2011-12-15 13:53:22 -0800 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. 522226 3 ap 2011-12-15 14:04:11 -0800 So, the rationale is "rarely used, and frequently implemented incorrectly". 848860 4 masa141421356 2013-03-06 07:45:19 -0800 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/ 1958587 5 annevk 2023-05-29 02:18:23 -0700 What is UTF7Encoding() about? Is that for WebKit embedders? If so, I suspect this is fixed as UTF-7 is blocklisted somewhere.