W3C home > Mailing lists > Public > www-style@w3.org > September 2013

Re: Making selectors first-class citizens

From: Brian Kardell <bkardell@gmail.com>
Date: Wed, 11 Sep 2013 10:50:01 -0400
Message-ID: <CADC=+jctUtssm13e8eVKg0JTBsEex4gJRXfrQadgPx9Pk5v63Q@mail.gmail.com>
To: Robin Berjon <robin@w3.org>
Cc: Anne van Kesteren <annevk@annevk.nl>, Domenic Denicola <domenic@domenicdenicola.com>, "www-style@w3.org" <www-style@w3.org>, WebApps WG <public-webapps@w3.org>
On Sep 11, 2013 10:04 AM, "Robin Berjon" <robin@w3.org> wrote:
>
> On 11/09/2013 15:56 , Anne van Kesteren wrote:
>>
>> On Wed, Sep 11, 2013 at 2:52 PM, Brian Kardell <bkardell@gmail.com>
wrote:
>>>
>>> I like the idea, but matches has been in release builds for a long time,
>>> right?  Hitch uses it.
>>
>>
>> <!DOCTYPE html>.<script>w("matches" in document.body)</script>
>> http://software.hixie.ch/utilities/js/live-dom-viewer/
>>
>> false in both Firefox and Chrome.
>
>
> See http://caniuse.com/#search=matches. You do get mozMatchesSelector
(and variants) in there.
>
>
> --
> Robin Berjon - http://berjon.com/ - @robinberjon

Yes, to be clear, that is what i meant. If it is in a draft and
widely/compatibly implemented and deployed in released browsers not behind
a flag - people are using it.  That's part of why we switched the general
philosophy right? No doubt one can be a shorthand for the better approach
though...right?
Received on Wednesday, 11 September 2013 14:50:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:34 UTC