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: Dimitri Glazkov <dglazkov@chromium.org>
Date: Tue, 22 Nov 2011 08:54:59 -0800
Message-ID: <CADh5Ky3MyF7eSQt=u=bp8xLrjqcLitvDc67nBrxT_Bmf3sJXtQ@mail.gmail.com>
To: Yehuda Katz <wycats@gmail.com>
Cc: Roland Steiner <rolandsteiner@chromium.org>, Boris Zbarsky <bzbarsky@mit.edu>, "Tab Atkins Jr." <jackalmage@gmail.com>, public-webapps@w3.org, Dominic Cooney <dominicc@chromium.org>
On Tue, Nov 22, 2011 at 12:18 AM, Yehuda Katz <wycats@gmail.com> wrote:
> Yehuda Katz
> (ph) 718.877.1325
>
>
> On Tue, Nov 22, 2011 at 12:14 AM, Roland Steiner
> <rolandsteiner@chromium.org> wrote:
>>
>> On Tue, Nov 22, 2011 at 14:19, Yehuda Katz <wycats@gmail.com> wrote:
>>>
>>> Yehuda Katz
>>> (ph) 718.877.1325
>>>
>>>
>>> On Mon, Nov 21, 2011 at 8:34 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
>>>>
>>>> On 11/21/11 11:31 AM, Tab Atkins Jr. wrote:
>>>>>>
>>>>>> 1)  Make sense.
>>>>>> 2)  Not break existing content.
>>>>>> 3)  Be short.
>>>>>
>>>>> .matches
>>>>> .is
>>>
>>> I like .is, the name jQuery uses for this purpose. Any reason not to go
>>> with it?
>>
>> IMHO 'is' seems awfully broad in meaning and doesn't very well indicate
>> that the parameter should be a selector. Inasmuch I like .matches better.
>
> It's really clear in actual usage:
> someElement.is("div a:first-child");

Please don't grab "is"! This is the property/attribute we want to use
to identify components:

<div is="foobarf"></div>
...
div.is == 'foobarf'

:DG<

>
>>
>> Also, FWIW, an 'is' attribute on elements was/is in discussion on this ML
>> as one possibility to specify components.
>>
>> Cheers,
>> - Roland
>
Received on Tuesday, 22 November 2011 16:55:36 GMT

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