Edit comment LC-1987 for Web Applications Working Group

Quick access to LC-1985 LC-1986 LC-1987 LC-1988 LC-1989 LC-1990

Comment LC-1987

Comment Shortname:

Commenter: Daniel Glazman <daniel.glazman@disruptive-innovations.com>

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeElement Traversal Specification /**/ .issue... W3C Editor's Draft 29 July 2008 Abstract Status of this Document Table of Contents 1. Introduction 1.1. Not in This Specification 1.2. Conformance 2. ElementTraversal interface 2.1. firstElementChild 2.2. lastElementChild 2.3. previousElementSibling 2.4. nextElementSibling 2.5. childElementCount 3. Examples of usage 3.1. Example of previousElementSibling 3.2. Example of Precalculating Values and Looping Through Elements 3.3. Example of Comparison with Other DOM Interfaces 4. Relationship to other DOM specifications 4.1. DOM Level 1 Core 4.2. DOM Level 2 Traversal & Range 4.3. DOM Level 3 Core 5. Security Considerations A. IDL Definitions firstElementChild lastElementChild previousElementSibling nextElementSibling childElementCount B. ECMAScript Language Binding C. Java Language Binding org/w3c/dom/ElementTraversal.java: D. Change History E. References Normative references [RFC2119] Key words for use in RFCs to indicate Requirement... RFC2119 [DOM1Core] Document Object Model - Level 1 Core DOM1Core [ECMA262] ECMAScript Language Specification, 3rd edition ECMA262 Informative references [SVGD] The proposed ElementTraversal interface in SVG SVGD [DOM2TR] The DOM 2 Traversal and Range Specification DOM2TR [DOM3Core] Document Object Model - Level 3 Core DOM3Core F. Acknowledgments
or

Refinement of the section concerned:

Status:

open proposal pending resolved_yes resolved_no resolved_partial other assigned to Nobody

Type: substantive editorial typo question general comment undefined

Resolution status:

Response drafted Resolution implemented Reply sent to commenter

Response status:

No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):

Comment:

Hi,

1. congrats for this spec, I love it ; I can't count how many times in
page or chrome script I am filtering out nodes that are not element
nodes.

2. the ElementTraversal interface has a |childElementCount| attribute
but misses access to an individual childElement based on its index.
That would be really useful. Two solutions here :

a. you remove the childElementCount attribute in favor of a

readonly attribute NodeList childElements;

and that NodeList has all we need

b. you add

Node item(in unsigned long index);

but that is not really consistent with the existing way of
querying list of nodes.

My very strong preference goes to solution a.

Best,

</Daniel>

Related issues: (space separated ids)

WG Notes: http://www.w3.org/2008/webapps/track/issues/6

Resolution: After much conversation and review of existing implementations, we resolved not to add a nodelist to Element Traversal, but to create a separate spec to add that and similar features. Commentor was satisfied: http://lists.w3.org/Archives/Public/public-webapps/2008AprJun/0396.html

(Please make sure the resolution is adapted for public consumption)