W3C home > Mailing lists > Public > public-webapi@w3.org > April 2007

Re: ElementTraversal spec draft

From: Doug Schepers <doug.schepers@vectoreal.com>
Date: Tue, 03 Apr 2007 11:50:12 -0400
Message-ID: <461277B4.4070208@vectoreal.com>
To: Web API public <public-webapi@w3.org>

Accidentally sent offlist to Boris.  Repeating here.  Boris replied to 
me as well, but I'll leave it to him to send that to the list if he wishes.


-------- Original Message --------
Subject: Re: ElementTraversal spec draft
Date: Fri, 16 Mar 2007 18:33:22 -0400

Hi, Boris-

Boris Zbarsky wrote:
> Charles McCathieNevile wrote:
>> If this is added, should the list be live or static? I am inclined to
>>  make this a static element list, a la the Selectors spec, since it
>> is intended to be a lightweight interface
> Why does that make it more lightweight?  Is that from an implementation
> standpoint, or a web-developer standpoint?
> For what it's worth, implementing a live list in Gecko is actually
> somewhat easier than implementing a non-live one...  There's just a
> generic class to do them.

Sure, on a established code base for a desktop browser, that makes
sense.  But on mobile devices with limited memory, maintaining a live
list is more overhead.  Also, I know of at least one SVG viewer
implementor who complained about having to create live nodelists from

ElementTraversal started as an interface for resource-restricted
devices, and I want it to continue to work for them.

Received on Tuesday, 3 April 2007 15:50:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:23 UTC