W3C home > Mailing lists > Public > www-style@w3.org > September 2009

Re: Supporting Scoped Selectors in Selectors API 2

From: L. David Baron <dbaron@dbaron.org>
Date: Mon, 28 Sep 2009 22:08:01 -0700
To: www-style <www-style@w3.org>
Message-ID: <20090929050801.GA14824@pickering.dbaron.org>
On Monday 2009-09-28 19:46 -0500, Tab Atkins Jr. wrote:
> On Mon, Sep 28, 2009 at 6:49 PM, Lachlan Hunt <lachlan.hunt@lachy.id.au> wrote:
> > elm.querySelectorAll(":reference+p, div div");
> >
> > Or the reverse of that:
> >
> > elm.querySelectorAll("div div, :reference+p");
> 
> I'm not sure what the problem here is.  Surely you have to parse the
> entire string before starting *anyway*.  What's wrong with saying
> that, if :reference is found anywhere in the selector, it's a scoped
> selector string?

I think one of the comma-separated selectors shouldn't influence
whether any of the other selectors in the group match.  The pieces
that are separated by commas (which css3-selectors calls selectors)
should be independent of each other.

-David

-- 
L. David Baron                                 http://dbaron.org/
Mozilla Corporation                       http://www.mozilla.com/
Received on Tuesday, 29 September 2009 05:08:41 GMT

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