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

Re: [SelectorsAPI] Thoughts on querySelectorAll

From: Jonas Sicking <jonas@sicking.cc>
Date: Wed, 30 Apr 2008 15:30:09 -0700
Message-ID: <4818F2F1.80407@sicking.cc>
To: John Resig <jresig@mozilla.com>
CC: public-webapi@w3.org

>> The added bonus of the current matching is that it does allow for the
>> selector to "leak" should you want that for whatever reason.
> 
> This isn't really important since this result can already be achieved in another manner, using .compareDocumentPosition() or .contains() (in IE). However, leaving it "broken by default because it would be hard to specify" doesn't really seem to mesh well.

True, though this would be significantly slower since the implementation 
would match against all nodes in the whole document, only to have many 
of them filtered out.

/ Jonas
Received on Wednesday, 30 April 2008 22:31:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 April 2008 22:31:31 GMT