W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > February 2011

[Bug 12148] I strongly believe disallowing 'true' and 'false' in boolean attributes will cause significant confusion in the future. Already, you can find respected web developers incorrectly referring to attributes as true and false. For instance: http://blog.getif

From: <bugzilla@jessica.w3.org>
Date: Mon, 21 Feb 2011 20:04:59 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Prc0B-0002iy-DG@jessica.w3.org>

Boris Zbarsky <bzbarsky@mit.edu> changed:

           What    |Removed                     |Added
                 CC|                            |bzbarsky@mit.edu

--- Comment #2 from Boris Zbarsky <bzbarsky@mit.edu> 2011-02-21 20:04:58 UTC ---
> Surely the last example cannot be equivalent.

It is.  Try it in any web browser.

The behavior of boolean attributes is something HTML4 required and that has
been implemented correctly by every single browser for well over a decade. 
There's no way to change it without breaking sites.

> I understand some of this comes from the original guideline


> while expanding the definition to include the human friendly variants "true"
> and "false".

Due to the way browsers work right now, there are sites specifying "false" as a
value for boolean attributes and expecting the "true" behavior.  Sad, but
that's the web for you.

> There is exactly one conflicting case, where the attribute is named "false". 

You're assuming all sites serve up validating HTML 4.  This is a bad

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 Monday, 21 February 2011 20:05:00 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:05 UTC