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

• From: Sean Hogan <shogun70@westnet.com.au>
• Date: Thu, 20 Oct 2011 18:01:50 +1100
• To: Jonas Sicking <jonas@sicking.cc>
• CC: Alex Russell <slightlyoff@google.com>, 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>
• Message-ID: <4E9FC75E.3080309@westnet.com.au>

On 20/10/11 5:41 PM, Jonas Sicking wrote:
> On Wed, Oct 19, 2011 at 11:14 PM, Sean Hogan<shogun70@westnet.com.au>  wrote:
>>> I do however like the idea that if :scope appears in the selector,
>>> then this removes the prepending of ":scope " to that selector group.
>>> Is there a reason not to do that?
>> 1. Already supported (in the draft spec) by querySelectorAll().
>> 2. Not supported by JS libs.
>> 3. No use cases requiring it.
> It's annoying if querying engines have to work with two different
> query methods (.findAll and .querySelectorAll) and know when to call
> which. So I don't think 1 is a particularly good point.

I don't follow that.
If you want <style scoped> behavior you call findAll().
If not you call querySelectorAll().

Sean

Received on Thursday, 20 October 2011 07:02:18 UTC