On May 1, 2007, at 2:40 PM, John Horner wrote:
Well perhaps your second point is valid (and well formed) but this
example:
body { background: url('image.gif')no-repeat top }
isn't just about cross-browser compatiblity. Surely without the
whitespace, it's actually invalid CSS? The same as it would be if
"no-repeat" and "top" appeared without space between?
I don't think it is invalid CSS - the closing parenthesis ')'
terminates the url value. The white-space is optional. I think.
For keywords, it is of course different 'top right' is not the same
as topright.
See for more:
<http://www.w3.org/TR/CSS21/syndata.html>
And as for the logic of HTML tags, it would undeniably be a better
validator if it could warn "tag-based declaration doesn't match any
known HTML element", the way Perl's error reporting warns me about
variables I've created but never used, on the basis that it's
probably a
typo.
The validator doesn't look/care about what you put in a selector.
What if you are using that css file for some xml document that has an
element 'navbar' within its namespace ?
Philippe
---
Philippe Wittenbergh
<http://emps.l-c-n.com>
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
