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

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

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Fri, 14 Mar 2008 16:25:18 -0500
Message-ID: <47DAED3E.2000809@mit.edu>
To: Jonas Sicking <jonas@sicking.cc>
CC: "Web APIs WG (public)" <public-webapi@w3.org>

Jonas Sicking wrote:
> If we merge DocumentSelector and ElementSelector into simply 
> NodeSelector we'll more or less automatically get the functions on 
> DocumentFragments.

Not necessarily.  I'm not advocating that all Nodes be castable to 
NodeSelector.  Just that whatever nodes querySelector(All) work on are.

> We'd also get it for attribute nodes which might be less desirable. 

I don't think it's desirable at all.

> Though we could say that the interface is only required to be 
> implemented on Documents, Elements and DocumentFragments.

That would be my suggestion, yes.  ;)

> 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.


That said, is there interest in getting this spec to CR quickly, since 
it seems some UAs are planning to ship it in the near future even though 
it's a Working Draft?  Or are said UAs willing to make changes to their 
implementation after shipping as the spec changes?

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

Again, agreed.

Received on Friday, 14 March 2008 21:26:01 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:25 UTC