W3C home > Mailing lists > Public > www-validator-css@w3.org > March 2008

Re: Malformed declarations incorrectly parsed?

From: Yves Lafon <ylafon@w3.org>
Date: Fri, 14 Mar 2008 12:16:13 -0400 (EDT)
To: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Cc: www-validator-css@w3.org
Message-ID: <Pine.LNX.4.64.0803141209480.3393@ubzre.j3.bet>

On Fri, 14 Mar 2008, Benjamin Hawkes-Lewis wrote:

> Yves Lafon wrote:
>> Yes, in case of error, the current behaviour is to skip until a matching 
>> brace. This might be changed in the future, but is part of a more general 
>> discussion about: "Should a _validator_ do error recovery like other UA 
>> like browsers, or not? The same apply for the examples below.
>
> Whatever the tool does needs to be consistent and explained. From the 
> erroneous input:

The tool is consistent... but it depends on the error case. Lexical errors 
are handled with a skip to matching brace, just add an error if a value is 
wrong, and in all cases everything already succesfully parsed remains. 
Clearly, "skip to matching brace" is useful to recover, but not in line 
with the error recovery scheme of the CSS21 spec.

> p {unknown: red; color: green;}
>
> The validator extracts color: green; as valid CSS information, rather than 
> dropping the rule set.
>
> In the spec examples:
>
> (a) p { color:green; color }
>
> (b) p { color:green; color: }
>
> (c) p { color:red;   color:; color:green }
>
> It does not drop the entire rule set, but instead reports color: green; in 
> all cases and color: red; in (c).
>
> --
> Benjamin Hawkes-Lewis
>

-- 
Baroula que barouleras, au tiéu toujou t'entourneras.

         ~~Yves
Received on Friday, 14 March 2008 16:16:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 June 2012 00:14:20 GMT