- From: Sean Hogan <shogun70@westnet.com.au>
- Date: Sun, 07 Dec 2008 06:52:33 +1100
- To: Charles McCathieNevile <chaals@opera.com>
- CC: public-webapps@w3.org
Gregory Reimer (the author of reglib) points out that Element.matchesSelector would be useful for event delegation. See http://blogs.sun.com/greimer/entry/opera_10_will_suport_selector It would also neatly tie in with NodeFilter in DOM-Traversal, facilitating something like a live querySelectorAll() during document load. Unfortunately I had assumed it was in the spec. I've looked now and seen that it wasn't considered due to a lack of presented use cases, which seems non-sensical. matchesSelector() is to querySelectorAll() as tagName is to getElementsByTagName(). The only reason for it not to be in the spec is if it is harmful. The only complication I can see is supporting the :scope pseudo-attribute. cheers, Sean Charles McCathieNevile wrote: > > Hi, > > Lachy thinks the latest editor's draft[1] is ready for Last Call, > after responding to all the comments from last time (and removing the > NSResolver). The disposition of comments[2] explains what happened to > those comments. > > So this is a call for Consensus to publish the Editor's Draft [1] of > the Selectors API spec as a Last Call. Please respond before Monday > November 10. As always, silence is taken as assent but an explicit > response is preferred. > > Opera supports publication of this draft as a Last Call. > > [1] http://dev.w3.org/2006/webapi/selectors-api/ > [2] > http://dev.w3.org/2006/webapi/selectors-api/disposition-of-comments.html > > cheers > > Chaals >
Received on Saturday, 6 December 2008 19:53:19 UTC