W3C home > Mailing lists > Public > public-webapi@w3.org > January 2007

Re: Selectors API updates

From: Anne van Kesteren <annevk@opera.com>
Date: Wed, 10 Jan 2007 00:14:35 +0100
To: "Web API WG (public)" <public-webapi@w3.org>
Message-ID: <op.tlwtileq64w2qv@id-c0020>

On Tue, 09 Jan 2007 23:08:01 +0100, Anne van Kesteren <annevk@opera.com>  
wrote:
> Now I'm wondering whether we need Element.matchesSelector(). Basically  
> you pass it a group of selectors and it returns true or false depending  
> on whether or not the element would've been matched. The use case so far  
> given is that this would make it possible to implement constructs like  
> XBL <content includes=""> in JavaScript. I assume there are others, but  
> I'm wondering whether it's really worth it.
>
>
> When that last issue is resolved I think the specification is ready for  
> Last Call (again).

I was told the above can wait to a future version. I don't really see the  
immediate need either and the suggestion has come up twice so far in  
slightly different ways without really convincing use cases so I suggest  
we move this specification to Last Call.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Tuesday, 9 January 2007 23:14:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:56 GMT