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 9049 - What is the correct behavior if a <meta http-equiv="Content-Type"> conflicts with <meta charset>?
Summary: What is the correct behavior if a <meta http-equiv="Content-Type"> conflicts ...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-17 10:51 UTC by contributor
Modified: 2010-10-04 14:57 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2010-02-17 10:51:10 UTC 
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
Comment 1 Ms2ger 2010-02-18 19:21:57 UTC 
The first one. (Found hidden in <http://www.whatwg.org/html/#documentEncoding>.)
Comment 2 Ian 'Hixie' Hickson 2010-02-25 06:35:36 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: 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.
Comment 3 Ian 'Hixie' Hickson 2010-02-25 06:36:21 UTC 
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.