- From: Sean Hogan <shogun70@westnet.com.au>
- Date: Tue, 22 Nov 2011 13:15:40 +1100
- To: Boris Zbarsky <bzbarsky@MIT.EDU>
- CC: "Tab Atkins Jr." <jackalmage@gmail.com>, public-webapps@w3.org
On 22/11/11 3:23 AM, Boris Zbarsky wrote:
> On 11/21/11 10:56 AM, Tab Atkins Jr. wrote:
>> On Mon, Nov 21, 2011 at 7:22 AM, Boris Zbarsky<bzbarsky@mit.edu> wrote:
>>> What's the current state of matchesSelector? Are we confident
>>> enough in the
>>> name and such to unprefix it?
>>
>> I think that matchesSelector suffers from the same verbosity that qSA
>> does, and would benefit from the same discussion as what has happened
>> over .find/findAll.
>
> I was wondering about that; hence the question.
>
> Let's have this discussion right now. What name here would:
>
> 1) Make sense.
The current defined behavior of matchesSelector() goes with the behavior
of querySelectorAll(), so the name seems appropriate.
If find / findAll is implemented then a matches() method with
corresponding behavior might be appropriate. See the discussion that
started at
http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/0342.html
Sean
Received on Tuesday, 22 November 2011 02:16:16 UTC