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

[Bug 3313] Validator does not accept comments between tokens

From: <bugzilla@wiggum.w3.org>
Date: Wed, 23 Aug 2006 08:29:48 +0000
CC:
To: www-validator-cvs@w3.org
Message-Id: <E1GFo7Q-0004Dv-8s@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3313





------- Comment #3 from cecil@cecilward.com  2006-08-23 08:29 -------
(In reply to comment #1)

Once again, I correct myself. I re-read the lexer specification from CSS2.1
april 2006 and I notice the rule that includes a preceding {s}+ as part of a
comment specification. So the authors are ahead of me. The rule immediately
above - a comment token alone - suggests that comments are not equal to
whitespace. (Which means I had been very wrong earlier.) Rather
whitespace+comment == whitespace. Yet there is no corresponding rule for to
cater for the case comment+whitespace, rather we have
comment+whitespace->whitespace whitespace. This suggests that an additional
rule (or possibly two rules) would fix the problem and there are various
choices.

I should not have said that the distribution of comments is not well described,
as with a few fixes of this kind comments would really disappear from the
grammar and it would almost be well described. We would also have to watch out
for the special case of css2.1 @charset (ought that to go into the lexer?) as
making comments disappear completely surely permits various illegal @charset
forms which contain comments (since we can't attempt to put the entire @charset
and its argument into the lexer as a single token surely). If that can be
fixed, then I think we have won.
Received on Wednesday, 23 August 2006 08:29:54 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:17:25 UTC