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

Re: [selectors-api] Why have two identical differently named interfaces?

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 18 Mar 2008 10:48:09 -0700
Message-ID: <47E00059.5020801@sicking.cc>
To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
CC: Anne van Kesteren <annevk@opera.com>, "Web APIs WG (public)" <public-webapi@w3.org>

Lachlan Hunt wrote:
> 
> Anne van Kesteren wrote:
>>
>> On Fri, 14 Mar 2008 01:18:27 +0100, Maciej Stachowiak <mjs@apple.com> 
>> wrote:
>>> Maybe the best solution would be to add a :scope pseudo-element which 
>>> is the target of the querySelectorAll call if not called on the 
>>> document. That would allow old-school JS library semantics just by 
>>> prepending ":scope ".
>>
>> :scope would also be nice for HTML5 <style scoped>.
> 
> In the interest of getting this specification to CR sooner rather than 
> later, I have decided not to include such a feature in this 
> specification, but I think it is worth considering for a future extension.

Sounds fine to me. But I still haven't heard anything regarding the 
original subject of this thread :)

Is there a reason not to merge these two interfaces and also let 
DocumentFragments implement it?

/ Jonas
Received on Tuesday, 18 March 2008 17:49:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 18 March 2008 17:49:28 GMT