- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 07 Oct 2009 17:31:44 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7829 --- Comment #1 from Oliver Hallam <oliver@cbcl.co.uk> 2009-10-07 17:31:44 --- It could also be that <INPUT readonly DISABLED></INPUT> is the desired result. The strongest argument for this is that an implementation is free to test for boolean attributes at any point during serialization; whereas if the value is important then it must be handled before character replacement. I suspect it is better to leave this difference implementation-dependant. In this case I would still argue for the definition to be changed, but to something more like the following: <new> The HTML output MUST output boolean attributes in minimized form. A boolean attribute is an attribute which is defined in the HTML 4.01 DTDs with a single allowed value (disregarding case differences) that is equal to the name of the attribute. If the value of a boolean attribute is not equal to its name disregarding case differences then an implementation MAY choose to treat it as a non-boolean attribute. </new> This allows for most flexibility in matching what implementations already do. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 7 October 2009 17:31:46 UTC