W3C home > Mailing lists > Public > www-style@w3.org > April 2012

Re: [css3-syntax] dash-match and includes-match tokens

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 16 Apr 2012 07:48:08 -0700
Message-ID: <CAAWBYDAtFHLEO6VHkeVeutN616rfA-YJswtonm35AUOgjLidow@mail.gmail.com>
To: Simon Sapin <simon.sapin@kozea.fr>
Cc: www-style list <www-style@w3.org>
On Mon, Apr 16, 2012 at 7:11 AM, Simon Sapin <simon.sapin@kozea.fr> wrote:
> Le 16/04/2012 14:18, Simon Sapin a écrit :
>> Instead, I suggest to remove these tokens entirely. This means that most
>> attribute selector operators would be made of two DELIM tokens. Selector
>> parsers based on css3-syntax would have to look ahead to parse these
>> operators. As an implementer, I think this is not a problem; but I don’t
>> know the details of other implementations.
>
> I see that |= (if two delim tokens instead of a single dash-match) can be
> ambiguous with a namespaced attribute name, but this is resolved by checking
> the next token (either a '=' delim or an ident).

Yes, some lookahead in the parser is required anyway - I'll be trying
to keep it to one-token - such as for parsing a class name (DELIM
followed immediately by IDENT or DIMENSION - anything else is a parse
error).  So, parsing the *-match selectors with one token of lookahead
is fine.

~TJ
Received on Monday, 16 April 2012 14:49:00 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:52 GMT