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 6613 - Allow <meta charset="UTF-8"/> in XHTML
Summary: Allow <meta charset="UTF-8"/> in XHTML
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2009-02-23 10:51 UTC by Lachlan Hunt
Modified: 2010-10-04 13:59 UTC (History)
4 users (show)

See Also:


Description Lachlan Hunt 2009-02-23 10:51:27 UTC
To address the use case of polyglot documents being served as either HTML or XHTML, we need to be able to use <meta charset> in XHTML documents.  Allowing UTF-8 only is sufficient to address this case.

This is the justification for allowing this:
* UTF-8 is one of the defaults for XML, and so allowing this has no detrimental effect.

* If UTF-16 is being used, the <meta charset> is not needed because of the BOM.

* The presence UTF-8 BOM cannot be relied upon to adequately address this use case because it is invisible metadata and non-trivial to output in all cases.

* Any other encoding would require the use of an XML declaration, but that can't be used in a polyglot document, or it would require HTTP headers to set the charset, in which case, <meta charset> is unnecessary anyway.

See recent IRC discussion of this issue.
Comment 1 Maciej Stachowiak 2010-03-14 13:16:58 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, 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:

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.