W3C home > Mailing lists > Public > public-webapi@w3.org > March 2008

Re: [selectors-api] Why no querySelector(All) on DocumentFragments?

From: Maciej Stachowiak <mjs@apple.com>
Date: Fri, 14 Mar 2008 16:04:34 -0700
Cc: Boris Zbarsky <bzbarsky@MIT.EDU>, "Web APIs WG (public)" <public-webapi@w3.org>
Message-Id: <CB876FE1-4F65-4406-880C-38BA64BE811D@apple.com>
To: Jonas Sicking <jonas@sicking.cc>


On Mar 14, 2008, at 1:56 PM, Jonas Sicking wrote:

>
>> I think ability to do element-rooted selector queries (either  
>> through a new method or a :scope pseudo-element) is more important,  
>> since it's needed to replicate the feature set of JS query libraries.
>
> If we could get a :scope pseudo-element that would be an excellent  
> solution IMHO, and would be great with scoped stylesheets as has  
> been pointed out elsewhere in the last few days.
>
> Is that something that should be defined by this WG? It would suck  
> to have to wait for Level 4 Selectors. Other WGs have defined  
> selectors, but I'm not sure how good of an idea that is.

I would prefer to see it in the Selectors spec, but it would have to  
come out of CR for that. Perhaps the editor of the Selectors spec  
(Hixie) would like to weigh in. Alternately, we could temporarily  
define the pseudo-element in the Selectors API spec.

> The alternative, defining another set of methods would be something  
> that we could do, but that solution feels a lot less appealing.

I agree, :scope seems more elegant, and parallel methods can't handle  
the "> span" immediate children use case very nicely.

Regards,
Maciej
Received on Friday, 14 March 2008 23:05:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 14 March 2008 23:05:16 GMT