W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: QSA, the problem with ":scope", and naming

From: Willison, Timothy <willisontp@epb.net>
Date: Thu, 20 Oct 2011 20:43:55 +0000
To: Tab Atkins Jr. <jackalmage@gmail.com>
CC: Jonas Sicking <jonas@sicking.cc>, Alex Russell <slightlyoff@google.com>, Boris Zbarsky <bzbarsky@mit.edu>, "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <9977F318-77F5-4C6E-A7E4-2946C04D1F3E@epb.net>
On Oct 20, 2011, at 4:34 PM, Tab Atkins Jr. wrote:

> On Thu, Oct 20, 2011 at 12:09 PM, Jonas Sicking <jonas@sicking.cc> wrote:
>> Let's do the general discussion about how live and non-live NodeLists
>> should behave in a separate thread.
> Yes, let's.  ^_^
>> The immediate question here is how should the returned object from
>> .findAll behave? Should it be mutable? Should you be able to insert
>> non-Nodes into it? Should it have all of the functions of
>> Array.prototype or just some subset? Should it have any additional
>> functions?
>> Since .findAll is a new function we have absolutely no constraints as
>> far as how NodeLists behave, we can simply return something that isn't
>> a NodeList.
> It should absolutely have all the Array functions.  I know that I want
> to be able to slice, append, forEach, map, and reduce the list
> returned by .find.

IMHO, the most useful thing would be to just return an Array of nodes so no further adjustment of the return value is required in selector engines.

> ~TJ
Received on Friday, 21 October 2011 14:13:29 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:36 UTC