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: Robert Koberg <rob@koberg.com>
Date: Sat, 26 Mar 2005 07:19:15 -0800
Message-ID: <42457D73.5070708@koberg.com>
To: www-html@w3.org

Bjoern Hoehrmann wrote:
> * Robert Koberg wrote:
> 
>>I generate XHTML/JSP/Velocity pages from XSL and XML. One thing always 
>>seems clumsy to me: that is, why was something like an INPUT's checked 
>>attribute be set to "checked" and not true/false?
> 
> 
> You can write SGML declarations such that for enumerated attribute
> values only the value must be specified so you can write
> 
>   <input ... checked> rather than
>   <input ... checked="checked">
> 
> Using true/false as in
> 
>   <input ... true>


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

Anyway, next I'll ask why is the following invalid?

<input ... checked="">

thanks,
-Rob

> 
> would look a bit odd, is more likely to clash with some other attribute
> value and is more difficult to extend ("true", "false" and some third
> value in the same value space is a bit odd, too).
Received on Saturday, 26 March 2005 15:19:16 GMT
Valid XHTML 1.0! Valid CSS! Site Map | Privacy Policy | Terms of Use | WebHeadStart.org © 2005 All Rights Reserved.