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

Anne van Kesteren <[email protected]>
Newsgroups gmane.comp.web.dom.general
Message-ID <CADnb78iyjMEqVpacsj9bwyeRCAFNHPuG6bzx2aWePpGqNwy7tw@mail.gmail.com>
I updated DOM to use the new "primitive".

On Sat, Aug 9, 2014 at 7:40 AM, Tab Atkins Jr. <[email protected]> wrote:
> On Fri, Aug 8, 2014 at 6:31 PM, Boris Zbarsky <[email protected]> wrote:
>> Looks like it, modulo the same observability issues Anne's current setup
>> has.
>
> If selector matching ever becomes observable, we've got to settle on a
> matching algorithm in general, not just for this simple case.  The
> spec still talks about matching in the natural way, evaluating the
> selector from left to right, rather than from right to left as
> browsers tend to do.

DOM might need updates for this too, depending on whether parsing
becomes observable. As currently defined closest() would parse
numerous times if not optimized.


-- 
http://annevankesteren.nl/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.