W3C home > Mailing lists > Public > public-html@w3.org > April 2014

Re: Elements array and query/queryAll methods

From: Eric Devine <devineej@gmail.com>
Date: Thu, 10 Apr 2014 11:44:12 -0400
Message-ID: <CAGYLO0JKCHwi5qUvHLXwSu5cw+B_5Wq-yOcc0c1ks6Ccp8EsGQ@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: Domenic Denicola <domenic@domenicdenicola.com>, Dean Edwards <dean.edwards@gmail.com>, Travis Leithead <travis.leithead@microsoft.com>, "public-html@w3.org" <public-html@w3.org>, "www-dom@w3.org" <www-dom@w3.org>
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 <annevk@annevk.nl>wrote:

> On Tue, Apr 8, 2014 at 8:13 PM, Domenic Denicola
> <domenic@domenicdenicola.com> 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/
Received on Thursday, 10 April 2014 15:44:40 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:38 UTC