[Bug 9049] What is the correct behavior if a <meta http-equiv="Content-Type"> conflicts with <meta charset>?

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9049


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-02-25 06:35:36 ---
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.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 25 February 2010 06:35:38 UTC