This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10260 - Meta charset handling during the parse should special-case UTF-16 and reject non-ASCII supersets
Summary: Meta charset handling during the parse should special-case UTF-16 and reject ...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P1 critical
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: https://bugzilla.mozilla.org/show_bug...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-29 11:08 UTC by Henri Sivonen
Modified: 2010-10-04 14:56 UTC (History)
4 users (show)

See Also:

Attachments

Description Henri Sivonen 2010-07-29 11:08:09 UTC 
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.
Comment 1 Ian 'Hixie' Hickson 2010-08-16 19:19:17 UTC 
Can alias resolution ever change whether something is an ASCII superset or not?
Comment 2 Ian 'Hixie' Hickson 2010-08-16 19:23:41 UTC 
UTF-16 to UTF-8 mapping is already done by the "change the encoding" algorithm.
Comment 3 Ian 'Hixie' Hickson 2010-08-16 19:26:20 UTC 
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.
Comment 4 contributor 2010-08-16 19:28:07 UTC 
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