Welcome to WebHeadStart.org

Web Technologies

Sponsored By

WebHeadStart.org is currently in beta.
Please pardon our appearance as we work to provide you with the most comprehensive reference on today's web technologies.

Interested in advertising on WebHeadStart? Become an advertising partner today!

[WWW-HTML Mailing List Archive Home] [Messages By Thread] [Messages By Date]

Re: why, e.g., input/@checked="checked" ?

From: David Dorward <david@dorward.me.uk>
Date: Sat, 26 Mar 2005 15:25:37 +0000
To: Robert Koberg <rob@koberg.com>
Cc: www-html@w3.org
Message-ID: <20050326152537.GB14917@us-lot.org>

On Sat, Mar 26, 2005 at 07:19:15AM -0800, Robert Koberg wrote:
> >  <input ... true>

> It is probably a lack of understanding in SGML, but I don't understand 
> why you use true there and not checked.

To demonstrate why having true/false as values for the checked
attribute would be a bad idea. It isn't a valid code example.
 
> Anyway, next I'll ask why is the following invalid?
> 
> <input ... checked="">

The _only_ value allowed for the attribute is 'checked'. A null string
is not 'checked' and so isn't allowed. If the attribute is present
then it must have the value 'checked'.

-- 
David Dorward                                      http://dorward.me.uk 
Received on Saturday, 26 March 2005 15:25:38 GMT
Valid XHTML 1.0! Valid CSS! Site Map | Privacy Policy | Terms of Use | WebHeadStart.org © 2005 All Rights Reserved.