W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2009

RE: [selectors-api] Summary of Feature Requests for v2

From: Mike Wilson <mikewse@hotmail.com>
Date: Thu, 24 Sep 2009 09:02:30 +0200
To: "'Lachlan Hunt'" <lachlan.hunt@lachy.id.au>
Cc: "'public-webapps'" <public-webapps@w3.org>
Message-ID: <01c401ca3ce4$fbf778b0$0a01a8c0@mikedeskxp>
Yes, the base for event delegation is certainly something
like that. I just wanted to make clear that the main reason
for adding this functionality (IMO) is event delegation.
I'll let event delegation library creators chime in on the
details on what is needed for making really efficient
behavioural/delegation implementations, and judge the merits
of various optimizations. There has f ex already been mention
of caching "parsed" selectors.

Best regards
Mike

Lachlan Hunt wrote:
> Mike Wilson wrote:
> > My first priority would be "Matches Selector", and see to that
> > it fulfills the needs for event delegation.
> 
> Is there any special functionality that would be needed to 
> achieve this? 
>   If I understand correctly, event delegation just needs to 
> be able to 
> check whether the event target element matches a given 
> selector.  So it 
> would be something like:
> 
> if (evt.target.matchesSelector(".foo>input.bar")) {
>     ...
> }
> 
> -- 
> Lachlan Hunt - Opera Software
> http://lachy.id.au/
> http://www.opera.com/
> 
Received on Thursday, 24 September 2009 07:03:17 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:33 GMT