- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 19 Jul 2007 10:40:56 +0000
- To: www-validator-cvs@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4870
Summary: Comment inside selector, with whitespace before and
after
Product: CSSValidator
Version: CSS Validator
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: CSS 2.1
AssignedTo: dave.null@w3.org
ReportedBy: cecil@cecilward.com
QAContact: www-validator-cvs@w3.org
Following on from my muddled comments wrt 3313
Test case 1:
a /**/ b { width:0}
is (still) reported as invalid. (Tested using direc input, "no special profile"
setting).
FYI, in contrast, compare this with the correct behaviour in each of the
following test cases:
Test case 2:
a /**/> b { width:0}
(which is correctly? reported as valid).
and
Test case 3:
a/**/ b { width:0}
Test case 4:
a /**/b { width:0}
all of which are correctly reported as valid.
This is part of a more general comments==/!=whitespace issue.
[OffTopic]. This issue is arguably related to the quality of the CSS 2.1 (say)
spec's appendix containing a rough formal grammar, which really does need to be
cleaned up to clarify the rules about the distribution of comments and
particularly [comment+whitespace] and [whitespace+comment] sequences.
I suggest that the validator team might like to pass on a comment to the CSS
people as a suggestion for inclusion in a (imo much needed) CSS2.11
clarification addendum. probably just need the rules in the appendix to be
fixed up a bit (poss, see the discussion wrt bug 3313).
Cecil Ward.
Received on Thursday, 19 July 2007 10:40:58 UTC