Bug 74610
| Summary: | Remove UTF-7 and UTF-32 support | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Anne van Kesteren <annevk> |
| Component: | Platform | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ap, cdumez, eoconnor, jshin, masa141421356, mjs, Ms2ger, syoichi |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: |
https://bugs.webkit.org/show_bug.cgi?id=159651 https://bugs.webkit.org/show_bug.cgi?id=10709 |
||
Anne van Kesteren
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
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
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
So, the rationale is "rarely used, and frequently implemented incorrectly".
Masahiro Yamada
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
What is UTF7Encoding() about? Is that for WebKit embedders? If so, I suspect this is fixed as UTF-7 is blocklisted somewhere.