W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: [Selectors API 2] Is matchesSelector stable enough to unprefix in implementations?

From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Date: Thu, 24 Nov 2011 09:46:16 +0100
Message-ID: <4ECE0458.8000200@lachy.id.au>
To: Sean Hogan <shogun70@westnet.com.au>
CC: Boris Zbarsky <bzbarsky@MIT.EDU>, public-webapps@w3.org
On 2011-11-23 23:38, Sean Hogan wrote:
> Are there any issues with:
>
> - If you want to use selectors with explicit :scope then you use
> querySelector / querySelectorAll / matchesSelector.
>
> - If you want to use selectors with :scope implied at the start of each
> selector in the selector list (as most js libs currently do) then you
> use find / findAll / matches.

The matches method will not change behaviour depending on whether or not 
there is an explicit :scope because it is always evaluated in the 
context of the entire tree.  There is never an implied :scope inserted 
into the selector, so there will not be two alternative matches methods.

-- 
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Received on Thursday, 24 November 2011 08:46:53 GMT

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