This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
For values of charset, the condition is "a supported ASCII-compatible character encoding or a UTF-16 encoding" but for the value extracted from content, the condition is "a supported encoding". Please update the condition for the value extracted from content to match the condition placed on the value of charset.
Oops.
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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments.
Checked in as WHATWG revision r5765. Check-in comment: Make the rules for <meta> processing for charset='' vs content='' attributes consistent. http://html5.org/tools/web-apps-tracker?from=5764&to=5765
mass-move component to LC1