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 12240 - "The values 'true' and 'false' are not allowed on boolean attributes." - this also implies that "false" is not a valid attribute name, since ... false="false" ... (meaning the "false" property is 'true') would not be permitted in XML serialization
Summary: "The values 'true' and 'false' are not allowed on boolean attributes." - this...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
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: 2011-03-04 16:48 UTC by contributor
Modified: 2011-08-04 05:04 UTC (History)
7 users (show)

See Also:


Attachments

Description contributor 2011-03-04 16:48:36 UTC
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#boolean-attributes

Comment:
"The values 'true' and 'false' are not allowed on boolean attributes." - this
also implies that "false" is not a valid attribute name, since ...
false="false" ... (meaning the "false" property is 'true') would not be
permitted in XML serialization

Posted from: 74.109.217.50
User agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.14) Gecko/20110218 Firefox/3.6.14
Comment 1 Kyle Simpson 2011-03-04 16:52:02 UTC
dupe of Bug #12148?
Comment 2 Tab Atkins Jr. 2011-03-04 16:52:28 UTC
...correct?  Is there a problem to be solved surrounding this?
Comment 3 Aryeh Gregor 2011-03-04 17:41:01 UTC
No, incorrect.  The note contradicts the normative text in this case.  The normative text says false="false" or true="true" is allowed for boolean attributes named "false" or "true".  But this is a sufficiently academic contradiction that maybe it doesn't need to be fixed.
Comment 4 Ms2ger 2011-03-08 19:02:20 UTC
Well, false=false isn't conforming either, because @false doesn't exist, so I'd argue there isn't a contradiction.
Comment 5 Aryeh Gregor 2011-03-08 23:52:44 UTC
You've got me there.
Comment 6 Ian 'Hixie' Hickson 2011-05-06 19:31:51 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: false="false" isn't allowed because "false" isn't the name of a boolean attribute, indeed.
Comment 7 Michael[tm] Smith 2011-08-04 05:04:09 UTC
mass-moved component to LC1