W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: QSA, the problem with ":scope", and naming

From: Alex Russell <slightlyoff@google.com>
Date: Wed, 19 Oct 2011 00:38:31 +0100
Message-ID: <CANr5HFU=P2upz=1QyPX9sZ4Xt=-VTRKCqxPqUxX87Y09uHikPQ@mail.gmail.com>
To: Erik Arvidsson <arv@chromium.org>
Cc: Webapps WG <public-webapps@w3.org>, Yehuda Katz <wycats@gmail.com>, John Resig <jeresig@gmail.com>, Paul Irish <paulirish@google.com>, Lachlan Hunt <lachlan.hunt@lachy.id.au>
On Tue, Oct 18, 2011 at 6:00 PM, Erik Arvidsson <arv@chromium.org> wrote:
> On Tue, Oct 18, 2011 at 09:42, Alex Russell <slightlyoff@google.com> wrote:
>> Ah, but we don't need to care what CSS thinks of our DOM-only API. We
>> can live and let live by building on ":scope" and specifying find* as
>> syntactic sugar, defined as:
>>  HTMLDocument.prototype.find =
>>  HTMLElement.prototype.find = function(rootedSelector) {
>>     return this.querySelector(":scope " + rootedSelector);
>>   }
>>   HTMLDocument.prototype.findAll =
>>   HTMLElement.prototype.findAll = function(rootedSelector) {
>>     return this.querySelectorAll(":scope " + rootedSelector);
>>   }
> I like the way you think. Can I subscribe to your mailing list?

Heh. Yes ;-)

> One thing to point out with the desugar is that it has a bug and most
> JS libs have the same but. querySelectorAll allows multiple selectors,
> separated by a comma and to do this correctly you need to parse the
> selector which of course requires tons of code so no one does this.
> Lets fix that by building this into the platform.

I agree. I left should have mentioned it. The resolution I think is
most natural is to split on "," and assume that all selectors in the
list are ":scope" prefixed and that. A minor point is how to order the
items in the returned flattened list are ordered (document order? the
natural result of concat()?).
Received on Tuesday, 18 October 2011 23:39:34 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:36 UTC