- From: Charles McCathieNevile <chaals@opera.com>
- Date: Thu, 15 Mar 2007 12:06:38 -0700
- To: "Ellen Siegel" <ellen.siegel@sun.com>, "web API" <public-webapi@w3.org>
Hi folks, there is a new draft of the ElementTraversal specification: http://dev.w3.org/cvsweb/~checkout~/2006/webapi/ElementTraversal/publish/ElementTraversal.html There are a few issues where the editors would like feedback: @@issue: should we add a childElements attribute that returns a list of elements? Advantages: lets authors use "for" looping structure; lets authors know the number of elements, in case they need to use that info in e.g. layout algorithms (var eachWidth = totalWidth / el.childElements.length;) Disadvantages: may add to the footprint 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 Should there be Java and/or ECAMscript bindings in the spec? Anyway, for your enjoyment. Comments as specified in the Status of the Document section of the draft, please. cheers Chaals -- Charles McCathieNevile, Opera Software: Standards Group hablo español - je parle français - jeg lærer norsk chaals@opera.com Try Opera 9.1 http://opera.com
Received on Thursday, 15 March 2007 19:06:49 UTC