Re: Weird browser bug (I think)

On Thu, 15 May 2003, Kevin Stone wrote: >Wow what boneheaded syntax will they come up with next. So in that case >selected="false" and checked="off" would evaluate to true. Would they not? It's gonna be browser dependent of course, but I suspect you're right. That's partly the cost of backwards-compatibility. :) The reasoning for it is that valueless element attributes are not valid XML. So rather than have some meaningful value for the previously valueless ones, the standard is to code those old values with a value equal to the name, for consistency. At least, that's how I read it. See the W3 spec for XHTML regarding attribute minimization: http://www.w3.org/TR/xhtml1/#h-4.5 And, on boolean attributes: http://www.w3.org/TR/xhtml1/#C_10 Best wishes, John. -- John C Worsley | Lead Programmer / Web Developer, Command Prompt, Inc. (503) 222-2783 | jlx@commandprompt.com | webmaster@thelinuxreview.com TheLinuxReview | News for Linux Users | http://www.thelinuxreview.com