W3C home > Mailing lists > Public > www-style@w3.org > January 2013

Re: [css3-syntax] Preserved vs. non-preserved tokens.

From: Simon Sapin <simon.sapin@kozea.fr>
Date: Sat, 19 Jan 2013 14:06:29 +0100
Message-ID: <50FA9A55.3000900@kozea.fr>
To: "www-style@w3.org" <www-style@w3.org>
Le 19/01/2013 13:54, Simon Sapin a écrit :
> In §3.5. Tree Construction:
>
>> preserved tokens
>>
>> The tokens that can appear in the tree are: ident, hash, string, url,
>> delim, number, percentage, dimension, unicode-range, whitespace,
>> comment, cdo, cdc, colon, semicolon, at-keyword, ], ), and }.
>>
>> Note: This means that the following tokens emitted by the tokenizer
>> stage will not appear in the stylesheet object: function, bad-string,
>> bad-url, [, (, {.
>
> However, §3.5.14. Consume a primitive happily returns bad-string or
> bad-url tokens. They should be parse errors instead.
>
> What about ], ), and }? Shouldn’t they be parse errors too?

By this I mean that maybe these tokens should be non-preserved, and 
"Consume a primitive" should trigger a parse error when encountering them.

The same applies with cdo and cdc tokens.


These tokens are never valid after tree construction. We could either 
have tree construction take care of them (make them non-preserved) or 
leave that to more specific parsers (selector, prelude of a given 
at-rule, value of a given property, etc.)

Either way, I don’t see a reason for treating cdo or ] differently from 
bad-string.

-- 
Simon Sapin
Received on Saturday, 19 January 2013 13:06:52 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:04 GMT