9049 2010-02-17 10:51:10 +0000 What is the correct behavior if a <meta http-equiv="Content-Type"> conflicts with <meta charset>? 2010-10-04 14:57:19 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#meta P3 normal LC 1 contributor ian ian mike Ms2ger public-html-admin public-html-wg-issue-tracking wycats public-html-bugzilla oldest_to_newest 32267 0 contributor 2010-02-17 10:51:10 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#meta Comment: What is the correct behavior if a <meta http-equiv="Content-Type"> conflicts with <meta charset>? Posted from: 76.126.116.8 by wycats@gmail.com 32421 1 Ms2ger 2010-02-18 19:21:57 +0000 The first one. (Found hidden in <http://www.whatwg.org/html/#documentEncoding>.) 32660 2 ian 2010-02-25 06:35:36 +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: Rejected Change Description: no spec change Rationale: This is part of a bigger question, like what happens if you have two <meta charset>s, or what happens if you have none, or if the HTTP headers conflict with them, or if they are wrong, and so on. In general, we don't explain what happens in error cases like this to authors, since authors shouldn't run into these cases if they follow the spec. :-) Therefore, the answers are only in the UA-specific parts, as Ms2ger points out. 32661 3 ian 2010-02-25 06:36:21 +0000 Just to clarify: you can't legally have a <meta http-equiv="Content-Type"> that conflicts with a <meta charset>. If it's not clear that that is not allowed, let me know; that's something that we can maybe fix.