This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The spec now says: ]] There must not be more than one meta element with any particular state in the document at a time. [[ This new restricion doesn't allow authors to workaround current user agent bugs and/or cross browsers issues related to treatment of <meta http-equiv="content-language" content="*" > as well as HTTP content-language headers.
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: The spec isn't intended to let you work around every bug in every browser. The bugs in browsers should be fixed. We shouldn't make the spec work around the bugs.
(In reply to comment #1) > Rationale: The spec isn't intended to let you work around every bug in every > browser. Of course not. Agreed. This is not such a case. Or rather, it is not all cases, just a single case. And the intention of fixing this bug is the eniterly opposite: Make sure that it is possible to implement what HTML5 says (about the large issues) be having some leeway in the smaller issues. The undeniable fact is that this bug allow exactly that. > The bugs in browsers should be fixed. We shouldn't make the spec work > around the bugs. I am not a vendor. It is the vendor's task to fix their browsers. When it comes to NCRs, then you want browsers/vendors to implement something which authors are not allowed to use. Thus, I get the impression from you that you expect vendors to implement the spec regardless of whether there exists for authors a way to workaround a browser limitation (adding a semicolon) or not. So whether authors are allowed to work around this issue has no bearing whatsoever on the browsers.
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: no new information provided