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

Re: [DOM4] NodeList should be deprecated

From: Anne van Kesteren <annevk@opera.com>
Date: Fri, 09 Mar 2012 08:57:57 +0100
To: "WebApps WG" <public-webapps@w3.org>, "Erik Arvidsson" <arv@chromium.org>, "Ryosuke Niwa" <rniwa@chromium.org>, "Ojan Vafai" <ojan@chromium.org>
Message-ID: <op.wav8evg464w2qv@annevk-macbookpro.local>
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.

Mutation observers uses NodeList too.


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Friday, 9 March 2012 07:58:28 GMT

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