W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2007

[whatwg] why, e.g., input/@checked="checked" ?

From: Henri Sivonen <hsivonen@iki.fi>
Date: Wed, 6 Jun 2007 12:31:25 +0300
Message-ID: <A7580A0C-0186-44FA-B2F5-624A3F771211@iki.fi>
On Jun 5, 2007, at 09:38, Ian Hickson wrote:

> On Sat, 23 Apr 2005, Henri Sivonen wrote:
>> On Mar 31, 2005, at 12:32, fantasai wrote:
>>>
>>> So, for example, I could use attribute minimalization to shorten the
>>> 'type="checkbox"' part like so:
>>>
>>>   <input checkbox checked>
>>
>> What should text/html flavor HTML5 conformance checkers allow? The
>> tendency has been towards browser reality as opposed the allowing all
>> SGMLisms.
>
> Has the spec made this clear enough?

It has. Thanks.

> (Should it be changed?)

Probably not.

Requiring lower case for the boolean attribute's canonical name (as  
value) certainly makes things friendly for clean and portable RELAX  
NG schemata and, thus, easier for me. It also makes things  
politically correct as far as XHTML5 goes. I can imagine, however,  
that someone else might see the case restriction as excessive.

-- 
Henri Sivonen
hsivonen at iki.fi
http://hsivonen.iki.fi/
Received on Wednesday, 6 June 2007 02:31:25 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:56 UTC