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

Re: Selector Parsing for Selectors API

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Tue, 30 Oct 2012 12:20:48 -0400
Message-ID: <508FFE60.4090608@mit.edu>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: www-style@w3.org
On 10/30/12 11:50 AM, Tab Atkins Jr. wrote:
> As for the actual parser, Syntax is minimal in what is restricted from
> being in a selector - it can contain literally anything except a { or
> } token.  As long as we make sure that these are appropriately handled
> as an error by a Selectors parsing spec, then Selectors can do pretty
> much whatever it wants with its own parser.

No, it can't, imo.  For example, it shouldn't define different parsing 
behavior from actual CSS selector parsing given the same token stream 
for the cases when the string is a valid selector.  In my opinion.

Received on Tuesday, 30 October 2012 16:21:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:23 UTC