12240 2011-03-04 16:48:36 +0000 "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 2011-08-04 05:04:09 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#boolean-attributes P3 normal --- 1 contributor ian ayg ian mike Ms2ger public-html-admin public-html-wg-issue-tracking w3c public-html-bugzilla oldest_to_newest 46333 0 contributor 2011-03-04 16:48:36 +0000 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 46334 1 w3c 2011-03-04 16:52:02 +0000 dupe of Bug #12148? 46335 2 jackalmage 2011-03-04 16:52:28 +0000 ...correct? Is there a problem to be solved surrounding this? 46346 3 ayg 2011-03-04 17:41:01 +0000 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. 46551 4 Ms2ger 2011-03-08 19:02:20 +0000 Well, false=false isn't conforming either, because @false doesn't exist, so I'd argue there isn't a contradiction. 46564 5 ayg 2011-03-08 23:52:44 +0000 You've got me there. 48200 6 ian 2011-05-06 19:31:51 +0000 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. 52773 7 mike 2011-08-04 05:04:09 +0000 mass-moved component to LC1