W3C home > Mailing lists > Public > www-validator-css@w3.org > August 2006

Re: Validator incorrectly reports validity for case of font-family _keyword_ that is enclosed in quotes

From: Cecil Ward <cecil@cecilward.com>
Date: Tue, 22 Aug 2006 15:29:06 +0100
To: <www-validator-css@w3.org>
Message-ID: <000001c6c5f7$5321dd00$0500a8c0@cecilibmr51>

Since despite best efforts, my posts don't seem to appear (although, I seem
to be successful when hitting RESPOND in the website), would someone be kind
enough to post the following three bug reports for me?

Regards,

Cecil Ward.

Bug reports follow:

===
***REPORT #1 of 3:

Validator incorrectly reports CSS1-validity for case of escape + space
(tested within property value)


The validator does not validate CSS1 correctly, it validates the example
below against CSS2 despite the fact that you select 

grammar=CSS1.
 
I believe that the following CSS fragment is illegal CSS1, if my reading of
CSS 1 is correct, yet the validator reports no 

error with grammar=CSS1 selected. 
--
Test case:

	element { color: r\65 d }

IMPORTANT NOTE: to reproduce this defect, grammar=CSS1 MUST be selected, in
which case the validator incorrectly reports 

success. (The example is valid CSS2.)
--

Reasoning: in CSS1 the space after the numeric escape sequence is not to be
stripped as in CSS2. So in CSS1 the property 

value is "re d", and only in the CSS2 grammar is the value "red". See the
productions for "escape" in CSS1 appendix B.

=== END OF REPORT #1


===
***REPORT #2 of 3:

Validator incorrectly reports failure when using CSS1 grammar -  incorrectly
parses full-length numeric escapes

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.

=== END OF REPORT #2


===
*** REPORT #3 of 3:

Validator incorrectly reports failure when using CSS2 grammar - parses
full-length numeric escapes incorrectly

I believe that the following CSS2 fragment is legal CSS, if my reading of
CSS 2 is correct, yet the validator incorrectly 

reports an error with grammar=CSS2 selected. Test case:

	selector { color: gr\000065en; }

Reasoning: in CSS2 no terminating space is required after a full-length
numeric escape sequence, filled out to the maximum of 

six characters. So in CSS2 the property value is "red". See the productions
for "escape" in the CSS2 grammar.


[FYI, compare 
	selector { color: gre\000065n; }
	selector { color: r\000065 d; }
both of which is correctly reported as valid. It seems to be that the parser
is reading characters after the sixth hex digit 

and parsing them as part of the number.]

=== END OF REPORT #3
Received on Tuesday, 22 August 2006 14:29:29 GMT

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