W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2012

Re: [DOM4] NodeList should be deprecated

From: Adam Klein <adamk@chromium.org>
Date: Mon, 12 Mar 2012 11:00:49 -0700
Message-ID: <CAEvLGcLmj1mRgqjFs9AUnjxQWcFVy1y+QajHUi5SjT0qwXC=Mg@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: WebApps WG <public-webapps@w3.org>, Erik Arvidsson <arv@chromium.org>, Ryosuke Niwa <rniwa@chromium.org>, Ojan Vafai <ojan@chromium.org>
On Thu, Mar 8, 2012 at 11:57 PM, Anne van Kesteren <annevk@opera.com> wrote:

> On Thu, 08 Mar 2012 23:24:45 +0100, Ojan Vafai <ojan@chromium.org> wrote:
>
>> Dynamic NodeLists have a significant memory and performance cost. Static
>> NodeLists are basically just under-powered arrays. We should just return
>> Node arrays from any new APIs that return a list of Nodes. I'd like to
>> see NodeList get similar treatment to hasFeature, i.e. a note that it not be
>> used for new APIs and possibly even the explicitly list the APIs allowed
>> to return them.
>>
>> I don't see the Dynamic/Static distinction in DOM4 or the HTML spec. Is
>> this specified anywhere?
>>
>
> We use the words "live" and "static".
>
>
>
>  For reference, this came up in WebKit with some new Regions APIs
>> https://bugs.webkit.org/show_**bug.cgi?id=80638<https://bugs.webkit.org/show_bug.cgi?id=80638>
>> .
>>
>
> Mutation observers uses NodeList too.


Though there's no reason they couldn't use arrays instead (they're not
live). In fact, that would make the API more self-consistent, since arrays
(of MutationRecords) are already part of the interface.

- Adam
Received on Monday, 12 March 2012 18:01:22 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:50 GMT