Re: "match a selectors string" in the DOM spec doesn't do what it wants to be doing
"Tab Atkins Jr." <[email protected]>
| Newsgroups | gmane.comp.web.dom.general |
|---|---|
| Message-ID | <CAAWBYDCRyEnRc=uaPAjZ4F4wYX9U_Q01TvX8fX9J6U6epUU1vg@mail.gmail.com> |
On Mon, Aug 4, 2014 at 5:42 AM, Anne van Kesteren <[email protected]> wrote: > On Mon, Aug 4, 2014 at 9:52 AM, Boris Zbarsky <[email protected]> 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