Re: [WSG] While we're on the subject of validators...

2007-04-30 Thread Philippe Wittenbergh


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:



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






***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



RE: [WSG] While we're on the subject of validators...

2007-04-30 Thread John Horner
> It's CSS validator. It doesn't validate cross-browser 
> compatability or the logic (or existence of) of HTML tags.

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?

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 information contained in this email and any attachment is confidential and
may contain legally privileged or copyright material.   It is intended only for
the use of the addressee(s).  If you are not the intended recipient of this
email, you are not permitted to disseminate, distribute or copy this email or
any attachments.  If you have received this message in error, please notify the
sender immediately and delete this email from your system.  The ABC does not
represent or warrant that this transmission is secure or virus free.   Before
opening any attachment you should check for viruses.  The ABC's liability is
limited to resupplying any email and attachments
==


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] While we're on the subject of validators...

2007-04-30 Thread Stuart Foulstone
Hi,

It's CSS validator. It doesn't validate cross-browser compatability or the
logic (or existence of) of HTML tags.

Stuart


On Tue, May 1, 2007 12:51 am, John Horner wrote:
> I recently came across two niggling CSS errors:
>
> 1)
>   body { background: url('image.gif')no-repeat top }
>
> Here, the coder has left no whitespace after the URL in the shorthand
> "background" declaration.
>
> Firefox is OK with it, IE doesn't display the image.
>
> 2)
>   #right navbar {width:400px;}
>
> Here the coder meant #right_navbar but missed the underscore. Obviously
> it doesn't work.
>
> The thing is, the W3 CSS validator passes them both. It even *fixes* the
> missing space in the first example and displays it like this:
>
> body {
>   background : url('image.gif') no-repeat top;
> }
>
> The second case is a little more complex, because logically, anything
> which isn't a class or an id should be an HTML tag. And there's no HTML
> tag "navbar". Yet. So that can't be valid CSS for any valid HTML
> document.
>
> Should I report this to someone?
>
> ==
> The information contained in this email and any attachment is confidential
> and
> may contain legally privileged or copyright material.   It is intended
> only for
> the use of the addressee(s).  If you are not the intended recipient of
> this
> email, you are not permitted to disseminate, distribute or copy this email
> or
> any attachments.  If you have received this message in error, please
> notify the
> sender immediately and delete this email from your system.  The ABC does
> not
> represent or warrant that this transmission is secure or virus free.
> Before
> opening any attachment you should check for viruses.  The ABC's liability
> is
> limited to resupplying any email and attachments
> ==
>
>
> ***
> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
> Help: [EMAIL PROTECTED]
> ***
>
>


-- 
Stuart Foulstone.
http://www.bigeasyweb.co.uk
BigEasy Web Design
69 Flockton Court
Rockingham Street
Sheffield
S1 4EB

Tel. 07751 413451


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



[WSG] While we're on the subject of validators...

2007-04-30 Thread John Horner
I recently came across two niggling CSS errors:

1)
body { background: url('image.gif')no-repeat top }

Here, the coder has left no whitespace after the URL in the shorthand
"background" declaration.

Firefox is OK with it, IE doesn't display the image.

2)
#right navbar {width:400px;}

Here the coder meant #right_navbar but missed the underscore. Obviously
it doesn't work.

The thing is, the W3 CSS validator passes them both. It even *fixes* the
missing space in the first example and displays it like this:

body {
  background : url('image.gif') no-repeat top;
}

The second case is a little more complex, because logically, anything
which isn't a class or an id should be an HTML tag. And there's no HTML
tag "navbar". Yet. So that can't be valid CSS for any valid HTML
document.

Should I report this to someone?

==
The information contained in this email and any attachment is confidential and
may contain legally privileged or copyright material.   It is intended only for
the use of the addressee(s).  If you are not the intended recipient of this
email, you are not permitted to disseminate, distribute or copy this email or
any attachments.  If you have received this message in error, please notify the
sender immediately and delete this email from your system.  The ABC does not
represent or warrant that this transmission is secure or virus free.   Before
opening any attachment you should check for viruses.  The ABC's liability is
limited to resupplying any email and attachments
==


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***