:45:08 -0700
To: Adobe Systems vha...@adobe.commailto:vha...@adobe.com
Cc: Anne van Kesteren ann...@opera.commailto:ann...@opera.com,
public-webapps@w3.orgmailto:public-webapps@w3.org
public-webapps@w3.orgmailto:public-webapps@w3.org
Subject: Re: [DOM4] Question about using sequenceT v.s., NodeList
On Mar 16, 2012, at 1:40 AM, Anne van Kesteren wrote:
On Fri, 16 Mar 2012 01:59:48 +0100, Vincent Hardy
vha...@adobe.commailto:vha...@adobe.com wrote:
b. Use sequenceT everywhere except where T=Node, in which case we
would use NodeList. This is consistent with DOM4 and inconsistent within
the
The main reason to keep NodeList is because we'd like to add other APIs to
NodeList in the future that operate on the Nodes in the list (e.g. remove).
I don't really see use-cases for wanting a similar thing with the other
cases here, so I think sticking with arrays of Ranges and Regions is fine.
Hello,
I am working on a proposal (http://wiki.csswg.org/spec/css3-regions/css-om) to
update the CSS Regions CSS OM APIs, and one of the changes is to make various
lists static. I see that the thread at
http://lists.w3.org/Archives/Public/public-webapps/2012JanMar/1068.html stemmed
from the
