- From: <bugzilla@jessica.w3.org>
- Date: Tue, 22 Feb 2011 00:58:41 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12148
Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Simetrical+w3cbug@gmail.com
--- Comment #7 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-02-22 00:58:41 UTC ---
(In reply to comment #1)
> I can't really think of a single example where someone is
> setting the value in markup of a boolean attribute to the string "false" and
> yet still intending for that attribute to be turned on. That's completely
> opposite semantics and makes no sense at all to me.
The way it happens in practice is:
1) Author fiddles around with the page, not sure exactly how everything works
because they're not HTML experts.
2) Author is trying different things to see what works, and sets some boolean
attribute = false somewhere to see if that helps.
3) Page works, author goes on his merry way. Author does not realize that the
"foo=false" actually means the same as "foo=true" or just "foo", because he's
not an HTML expert, only has a vague idea of what "foo" is supposed to do to
begin with, and can't really be bothered in figuring it out now that the page
works.
It should be fairly easy to search public web pages to look for boolean
attributes set to false. http://www.dotnetdotcom.org/ has a
publicly-downloadable index snapshot. Experience suggests that you'll find a
nontrivial number of sites that misuse the attributes this way, but you're
welcome to try.
--
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 00:58:43 UTC