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

From: Anne van Kesteren <annevk@annevk.nl>
Date: Mon, 4 Aug 2014 14:42:30 +0200
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, "www-dom@w3.org" <www-dom@w3.org>
Message-ID: <CADnb78in3bFcwD1OqkmXQfOk7KoDqsueXn8sqXNP65Zqq9EcbQ@mail.gmail.com>

On Mon, Aug 4, 2014 at 9:52 AM, Boris Zbarsky <bzbarsky@mit.edu> 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/

Received on Monday, 4 August 2014 12:42:57 UTC