This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1073 - CSS3: Required "Rules for handling parsing errors" not working
Summary: CSS3: Required "Rules for handling parsing errors" not working
Status: RESOLVED FIXED
Alias: None
Product: CSSValidator
Classification: Unclassified
Component: Other (show other bugs)
Version: CSS Validator
Hardware: All All
: P2 major
Target Milestone: ---
Assignee: Olivier Thereaux
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-07 11:31 UTC by Christian Roth
Modified: 2008-03-17 14:34 UTC (History)
0 users

See Also:


Attachments

Description Christian Roth 2005-02-07 11:31:28 UTC
Trying to parse this example

p { color:red;   color{;color:maroon}; color:green }

from <http://www.w3.org/TR/CSS21/syndata.html#parsing-errors>, "Malformed declarations", does 
not deliver the result as required by the specification which should be:

p { color:green }

Similar problems occur in some of the other examples for malformed declarations from the spec.
Comment 1 Bj 2005-02-07 11:41:01 UTC
That's because the CSS Validator makes no attempt at supporting CSS 2.1 and 
these things have essentially undefined behavior in CSS 2.0.
Comment 2 Christian Roth 2005-02-07 12:32:01 UTC
Björn, you are right. I'm updating my report so that it reflects that it is only valid for CSS3, see:

<http://www.w3.org/TR/2003/WD-css3-syntax-20030813/#error-handling>

The profile selector offers CSS3 as a supported level, so it should work in that mode. However, it 
doesn't and produces the same erroneous validated stylesheet.
Comment 3 Yves Lafon 2008-03-17 14:34:48 UTC
http://www.w3.org/TR/CSS2/syndata.html#parsing-errors
is saying:
"In some cases, user agents must ignore part of an illegal style sheet. This specification defines ignore to mean that the user agent parses the illegal part (in order to find its beginning and end), but otherwise acts as if it had not been there.". To me, it matches the examples in http://www.w3.org/TR/CSS21/syndata.html#parsing-errors regarding malformed declarations, and what was defined already for invalid at-keywords.

It is now fixed and should parse all the "malformed declaration" section, as written in the examples.
See http://qa-dev.w3.org:8001/css-validator/