Re: [Selectors API 2] Is matchesSelector stable enough to unprefix in implementations? from Boris Zbarsky on 2011-11-25 (public-webapps@w3.org from October to December 2011)

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 24 Nov 2011 20:21:44 -0500
To: Sean Hogan <shogun70@westnet.com.au>
CC: Lachlan Hunt <lachlan.hunt@lachy.id.au>, public-webapps@w3.org
Message-ID: <4ECEEDA8.6090001@mit.edu>

On 11/24/11 7:07 PM, Sean Hogan wrote:
> If and when there is a need for a matching method that does imply :scope
> (which I provided a use-case for in
> http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/0342.html)

That's a use case passing in an explicit reference node.  If you're 
doing that, then it seems like using an explicit :scope in the selector 
would be just fine.  But I'll accept that in some sort of edge cases you 
can't do that.

> then it could be called matches().

That seems backwards: "does this node match this selector?" is the 
common use case, so should have the shorter name, no?

-Boris

Received on Friday, 25 November 2011 01:22:20 UTC