W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2014

Re: Behavior of matches() and closest() with :scope()

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 2 Sep 2014 18:20:00 +0200
Message-ID: <CADnb78jkq8aZ+Di5vAtJuK6yW6JEkbfCwEBNDCxSsbqArb=Qrg@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, "www-style@w3.org" <www-style@w3.org>, "www-dom@w3.org" <www-dom@w3.org>, David Håsäther <hasather@gmail.com>
On Tue, Sep 2, 2014 at 6:11 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> #1 is what I was intending, but looking at closest() now, I don't see
> a restriction to just compound selectors.  If complex selectors are
> allowed, then I guess it makes more sense to match matches() and have
> :scope refer to the element you're matching against.  It makes it
> harder to do some things, but they're probably rare and can be handled
> explicitly anyway.

Hmm yes, so 2) then? :-)

Received on Tuesday, 2 September 2014 16:20:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:23 UTC