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 372 - Too many value terms accepted in declaration
Summary: Too many value terms accepted in declaration
Alias: None
Product: CSSValidator
Classification: Unclassified
Component: CSS 1.0 (show other bugs)
Version: CSS Validator
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: Philippe Le Hegaret
QA Contact: qa-dev tracking
: 157 (view as bug list)
Depends on:
Reported: 2003-10-31 11:02 UTC by Marco Bonetti
Modified: 2005-08-08 13:05 UTC (History)
3 users (show)

See Also:

Too many terms in CSS-2.1 declarations (10.02 KB, text/css; charset=UTF-8)
2004-10-03 10:27 UTC, Etan Wexler

Description Marco Bonetti 2003-10-31 11:02:32 UTC
The following validates as valid CSS.

/* --- start of test case --- */

a valid rule {color: red; }

a broken rule {
 /* look-out: too many values! */
 margin: 0 0 0 0 0 0 0 0;

This string still validates! (the above rule probably broke the parsing)

/* --- end of test case --- */
Comment 1 Etan Wexler 2004-10-03 00:16:55 UTC
*** Bug 157 has been marked as a duplicate of this bug. ***
Comment 2 Etan Wexler 2004-10-03 10:27:33 UTC
Created attachment 373 [details]
Too many terms in CSS-2.1 declarations

For each non-deprecated property in CSS 2.1, there is at least one declaration.
Each declaration's value gives one too many terms. Thus every declaration
(every line but the first and last) should raise an error.
Comment 3 Sijtsche Smeman 2004-11-25 13:46:02 UTC
Is this bug still valid? I don't think so. My output gives a parsing error on 
the broken rule.

URI : file://localhost/TextArea
Line: 7 Context : a broken rule 
Invalid number : marginParse Error - 0 

Line: 12 Context : This string still validates 
Parse Error - [empty string] 

Valid CSS information
a valid rule {
color : red; 
Comment 4 Etan Wexler 2004-11-25 15:51:08 UTC
Check the test-case attachment. Results are at

The validator catches some of the errors, but lets some pass. The specific error
crafted by the original reporter is now caught. The bug, as reformulated in a
general way, remains valid.

Please write more test cases. (Or a conformant parser. And get me a sandwich
while youre at it.)
Comment 5 Yves Lafon 2005-08-08 13:05:43 UTC
Fixed with today's commit, the online version will be up soon on