Re: "match a selectors string" in the DOM spec doesn't do what it wants to be doing

On Mon, Aug 4, 2014 at 9:52 AM, Boris Zbarsky <[email protected]> wrote:
> Not to mention that if selector matching ever becomes observable (something
> people keep asking for with JS callbacks for pseudo-classes) the clever
> algorithm in the DOM spec becomes observably different from the sane way to
> implement matches().

Fair.


> 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.


-- 
http://annevankesteren.nl/