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 3628 - Validator incorrectly reports failure when using CSS1 grammar - incorrectly parses full-length numeric escapes
Summary: Validator incorrectly reports failure when using CSS1 grammar - incorrectly ...
Status: RESOLVED FIXED
Alias: None
Product: CSSValidator
Classification: Unclassified
Component: CSS 1.0 (show other bugs)
Version: CSS Validator
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-26 00:20 UTC by CecilWard
Modified: 2007-10-23 21:29 UTC (History)
0 users

See Also:


Attachments

Description CecilWard 2006-08-26 00:20:15 UTC
The validator does not parse CSS1 escapes correctly, it validates the example below against CSS2 despite the fact that you select grammar=CSS1.
 
I believe that the following CSS fragment is legal CSS1, if my reading of CSS 1 is correct, yet the validator incorrectly reports an error with grammar=CSS1 selected. 
--
Test case:

	selector { color: r\0065d; }


IMPORTANT NOTE: to reproduce this defect, grammar=CSS1 must be selected.  (The example is not valid CSS2.)
--

Reasoning: in CSS1 no space is used after the numeric escape sequence, and if filled out to the maximum of four characters, no terminator is required. So in CSS1 the property value is "red". See the productions for "escape" in CSS1 appendix B.

Regards,

Cecil Ward.
Comment 1 Olivier Thereaux 2007-07-19 09:29:40 UTC
This looks fixed since Bug #3627 was fixed. Keeping opened until we are sure that it is fixed, and have test cases.
Comment 2 CecilWard 2007-10-23 21:29:19 UTC
(In reply to comment #1)
> This looks fixed since Bug #3627 was fixed. Keeping opened until we are sure
> that it is fixed, and have test cases.

Looks good to me now. Can close this bug as FIXED.