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: Tue, 22 Feb 2011 01:01:28 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Prgd6-000595-Vx@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12148

--- Comment #8 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-02-22 01:01:28 UTC ---
Just to expand on the "experience suggests" part: with every new release,
browser implementers all get lots of bugs filed complaining about broken pages.
 They get a very good idea of what sorts of changes will result in an
unacceptable level of compatibility complaints from users.  So realize that you
are, in fact, probably wrong about the compatibility impact, if browser
implementers think you are, since they know about this sort of thing
first-hand.  But if you want to try making a case anyway, go ahead.

-- 
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 Tuesday, 22 February 2011 01:01:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 February 2011 01:01:39 GMT