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 9048 - "If either name, http-equiv, or itemprop is specified, then the content attribute must also be specified. Otherwise, it must be omitted." Might be more clearly stated as "If charset is specified, then the content attribute must be omitted. Otherwise it mu
Summary: "If either name, http-equiv, or itemprop is specified, then the content attri...
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:49 UTC by contributor
Modified: 2010-10-04 13:58 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-02-17 10:49:47 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#meta

Comment:
"If either name, http-equiv, or itemprop is specified, then the content
attribute must also be specified. Otherwise, it must be omitted." Might be
more clearly stated as "If charset is specified, then the content attribute
must be omitted. Otherwise it must be specified"

Posted from: 76.126.116.8 by wycats@gmail.com
Comment 1 Ian 'Hixie' Hickson 2010-02-23 10:58:59 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: Yeah, I considered that. I also considered "The content attribute must be specified unless the charset attribute is specified, in which case it must be omitted". However, upon comparing the three, I came to the conclusion they were all pretty confusing. The one in the spec is the only one that clearly makes the link between the attributes that need content="" and the content="" attribute, rather than linking content="" specifically to the one attribute that _doesn't_ need it (charset=""), which seemed to be a slight win.