Re: Behavior of matches() and closest() with :scope()
"Tab Atkins Jr." <[email protected]>
| Newsgroups | gmane.comp.web.dom.general,gmane.comp.web.css.general |
|---|---|
| Message-ID | <CAAWBYDDLVsfrdsR2Ukhw3RGs7Y7Pyb7CvS9ZG-OeDv-9mbP2hQ@mail.gmail.com> |
On Tue, Sep 2, 2014 at 9:20 AM, Anne van Kesteren <[email protected]> wrote: > On Tue, Sep 2, 2014 at 6:11 PM, Tab Atkins Jr. <[email protected]> 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? :-) Yes, sorry I didn't make that clear. ~TJ