tedd wrote:
At 8:47 PM -0400 6/17/09, Robert Cummings wrote:
tedd wrote:
As I understand it and is my experience, that is true -- a
stand-alone HTML attribute should be equal to itself, such as
selected="selected", or more specifically selected="SELECTED".
How is that MORE specific? XHTML is like a cross-section of XML and
HTML. It is case sensitive, so using an uppercase value in this
context is LESS specific.
Cheers,
Rob:
It's by definition that case-sensitive is more specific than
case-insensitive -- for example with respect to case-insensitive
"selected", "SELECTED", and "SeLeCtEd" are all the same whereas case
sensitive is more specific. Is this not true?
Or do you have a different definition that states more variety is
more specific?
As far as using selected="selected" or selected="SELECTED", I prefer
the latter -- but I don't think it makes much difference. Do you see
otherwise?
The spec says set the attribute value equal to the name of the attribute
itself. XHTML has case sensitive attributes. You have not set the value
equal to the attribute name, you have set it equal to the uppercase
transformation of the attribute name. if it were a password, most
systems wouldn't let you in. Fortunately for you, there's a zillion
others out there that follow instructions according to their own
internal (oft misguided) interpretation, and so the browser developers
decided to ignore case sensitivity. I only added a comment because you said:
selected="selected", or more specifically selected="SELECTED"'
In which case you've suggested the latter format is more correct... I
disagree for the aforementioned reasons.
Cheers,
Rob.
--
http://www.interjinn.com
Application and Templating Framework for PHP
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
