10260 2010-07-29 11:08:09 +0000 Meta charset handling during the parse should special-case UTF-16 and reject non-ASCII supersets 2010-10-04 14:56:47 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All RESOLVED FIXED https://bugzilla.mozilla.org/show_bug.cgi?id=582788 P1 critical --- 1 hsivonen ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 37161 0 hsivonen 2010-07-29 11:08:09 +0000 The tree builder spec says about meta: "If the element has a charset attribute, and its value is a supported encoding, and the confidence is currently tentative, then change the encoding to the encoding given by the value of the charset attribute." Instead, of merely considering "supported encoding", UTF-16 should be mappend to UTF-8 and after alias resolution non-ASCII-superset encodings should be treated as unsupported. 37462 1 ian 2010-08-16 19:19:17 +0000 Can alias resolution ever change whether something is an ASCII superset or not? 37463 2 ian 2010-08-16 19:23:41 +0000 UTF-16 to UTF-8 mapping is already done by the "change the encoding" algorithm. 37464 3 ian 2010-08-16 19:26:20 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Partially Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments, notwithstanding additional comments above. 37465 4 contributor 2010-08-16 19:28:07 +0000 Checked in as WHATWG revision r5295. Check-in comment: <meta charset> should only work for ASCII-compatible encodings. http://html5.org/tools/web-apps-tracker?from=5294&to=5295