Re: "match a selectors string" in the DOM spec doesn't do what it wants to be doing from Tab Atkins Jr. on 2014-08-08 (www-dom@w3.org from July to September 2014)

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 8 Aug 2014 15:02:21 -0700
To: Anne van Kesteren <annevk@annevk.nl>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, "www-dom@w3.org" <www-dom@w3.org>
Message-ID: <CAAWBYDCRyEnRc=uaPAjZ4F4wYX9U_Q01TvX8fX9J6U6epUU1vg@mail.gmail.com>

On Mon, Aug 4, 2014 at 5:42 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
> On Mon, Aug 4, 2014 at 9:52 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
>> I'm not proposing getting rid of "evaluate a selector"; I'm proposing
>> explicitly exposing the lower-level "does this selector match this element"
>> primitive and using it directly in matches() and closest().
>
> Sounds good. Will add this once Tab provides the primitive.

I think this does what you want?
http://dev.w3.org/csswg/selectors/#match-against-element

~TJ

Received on Friday, 8 August 2014 22:03:08 UTC