Edit comment LC-1989 for Web Applications Working Group

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

Comment LC-1989

Comment Shortname:

Commenter: João Eiras <joao.eiras@gmail.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.

The Element Traversal WD define childElementCount on the Element interface.
Personally I see little use for such property by itself.
It would make much more sense to have childElements (similar to childNodes
on Node), and therefore we could use childElements.length to get the same
value as childElementCount. childElements would also be a live NodeList.

Most use cases for Element only transversal require looping NodeLists, and
if the author still has to filter nodes from these NodeLists by their
nodeType, then that beats the entire purpouse of this specification.

Thank you.

Related issues: LC-1987
(space separated ids)

WG Notes: Comment made after LC. Duplicate comment to issue raised by Daniel Glazman, no new information. Replied to commentor: http://lists.w3.org/Archives/Public/public-webapps/2008JulSep/0284.html

Resolution: No change made.

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