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

• From: Anne van Kesteren <annevk@annevk.nl>
• Date: Mon, 1 Sep 2014 18:48:15 +0200
• To: "www-style@w3.org" <www-style@w3.org>, "www-dom@w3.org" <www-dom@w3.org>
• Cc: Boris Zbarsky <bzbarsky@mit.edu>, "Tab Atkins Jr." <jackalmage@gmail.com>, David Håsäther <hasather@gmail.com>
• Message-ID: <CADnb78h-zzcVUFnNiiRBsrrYXDqpChg3+_OY_GDmijU7B3qBMw@mail.gmail.com>

In https://bugzilla.mozilla.org/show_bug.cgi?id=886308#c29 bz points
out that I introduced a regression relative to the old definition of
matches() with the new hook in Selectors.

I guess the way to fix this for matches() would be to add a :scope
elements argument. What about closest(), should it have that argument
too?

I'm not too familiar admittedly with what would be desirable here.


-- 
http://annevankesteren.nl/

Received on Monday, 1 September 2014 16:48:41 UTC