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

Re: Malformed declarations incorrectly parsed?

From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Date: Tue, 18 Mar 2008 07:04:12 +0000
Message-ID: <47DF696C.60107@googlemail.com>
To: Yves Lafon <ylafon@w3.org>
CC: www-validator-css@w3.org

Yves Lafon wrote:
> On Sat, 15 Mar 2008, Benjamin Hawkes-Lewis wrote:
> 
>> Yves Lafon wrote:
>>> The tool is consistent... but it depends on the error case. Lexical 
>>> errors are handled with a skip to matching brace,
>>
>> That doesn't appear to be true.
>>
>> p { color:red; color:; color:green }
>>
>> includes a lexical error since "color:;" cannot be parsed as "property 
>> ':' S* expr prio?" from:
>>
>> http://www.w3.org/TR/CSS21/grammar.html#scanner
>>
>> The validator calls it a "parse error".
>>
>> If what you were saying were true, the validator would skip to the 
>> matching brace, but instead it reports color: green; as valid CSS 
>> information.

[snip]

> I dug a bit more in the code, and found the culprit. while skipStatement 
> was correctly skipping {} blocks, it was not the case for 
> skipAfterExpression (responsible for errors happening when parsing right 
> hand side of <prop> : <value>. Now fixed and in place at:
> 
> http://qa-dev.w3.org:8001/css-validator/

Hmm. I tried this with the very same example and it still extracts:

p {
color : red;
color : green;
}

Does that not happen for you?

--
Benjamin Hawkes-Lewis
Received on Tuesday, 18 March 2008 07:04:53 GMT

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