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

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 21 Nov 2011 08:31:59 -0800
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: public-webapps@w3.org
Message-ID: <CAAWBYDABt8R0rhjAYgWihWOTorMna-siSyQHMj5pqRECf_q_Bw@mail.gmail.com>

On Mon, Nov 21, 2011 at 8:23 AM, Boris Zbarsky <bzbarsky@mit.edu> 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.
> 2)  Not break existing content.
> 3)  Be short.

.matches
.is

~TJ

Received on Monday, 21 November 2011 16:32:52 UTC