Re: Elements array and query/queryAll methods
Eric Devine <[email protected]>
| Newsgroups | gmane.comp.web.dom.general |
|---|---|
| Message-ID | <CAGYLO0JKCHwi5qUvHLXwSu5cw+B_5Wq-yOcc0c1ks6Ccp8EsGQ@mail.gmail.com> |
If the intent is to provide jQuery-inspired Element collections, it seems natural to add some selector filtering like the Element.prototype.matches to the Elements subclass. Has there been any discussion on that? On Thu, Apr 10, 2014 at 11:30 AM, Anne van Kesteren <[email protected]>wrote: > On Tue, Apr 8, 2014 at 8:13 PM, Domenic Denicola > <[email protected]> wrote: > > Hmm, perhaps I misunderstood---I thought you were talking about creating > duplicates via `push` etc., but it sounds like you are worried about > duplicates in the result of `queryAll`? If so, then yes, I agree there > should not be duplicates in that result. It may be a mismatch between my > "polyfill" (which was meant to be more illustrative than anything) versus > the actual spec. > > How does it return duplicates? That would be rather strange. There is > a problem at the moment with Elements.prototype.query() and queryAll() > not doing proper filtering. Mostly awaiting some proper hooks for that > and the arrival of subclassing in general. > > > -- > http://annevankesteren.nl/ >