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 6614 - Restricting multiple character encoding declarations per document
Summary: Restricting multiple character encoding declarations per document
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 13:29 UTC by Lachlan Hunt
Modified: 2010-10-04 14:57 UTC (History)
5 users (show)

See Also:


Description Lachlan Hunt 2009-02-23 13:29:53 UTC
The spec states

"There must not be more than one meta element with a charset attribute per document."

This requirement fails to take into account character encoding declarations using:

  <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">

The requirement should instead state that there must not be more than one meta element used as a character encoding declaration per document.  This should make it clear that only one of either <meta charset> or <meta http-equiv="Content-Type" ...> may appear.
Comment 1 Simon Pieters 2009-02-23 13:40:54 UTC
there's a requirement in the "encoding declaration state" text that prevents having both <meta charset> and <meta content...>

although i agree it could be clearer

e.g. by being a bullet-point in the list of requirements for encoding declarations
Comment 2 Olivier Gendrin 2009-02-23 15:29:39 UTC
And in the case of multiples declarations, which one will be taken into account ?
Comment 3 Ian 'Hixie' Hickson 2009-04-01 01:54:34 UTC
the spec already defines how to handle multiple decls.

I've added the bullet point like was suggested.
Comment 4 Maciej Stachowiak 2010-03-14 13:16:59 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.