Edit comment LC-1986 for Web Applications Working Group

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

Comment LC-1986

Comment Shortname:

Commenter: KUROSAWA, Takeshi <taken.spc@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:

Dear Web API WG,

Element Traversal Spec uses "attribute" word at ECMAScript Language Biding[1].

> firstElementChild
> This read-only attribute is of type Element.

But it is prefered to use "property" rather than "attribute" in
ECMAScript world. Other DOM Specs use "property" at ECMAScript
Language Binding (ex. DOM Level 1[2], ...).
The biding should be something like below:

firstElementChild
This read-only property is of type Element.
...
childElementCount
This read-only property is of type Number.


Regards

1: http://www.w3.org/TR/2008/WD-ElementTraversal-20080303/#ecmascript-bindings
2: http://www.w3.org/TR/REC-DOM-Level-1/ecma-script-language-binding.html

Related issues: (space separated ids)

WG Notes:

Resolution: Spec changed in response to comment: http://lists.w3.org/Archives/Public/public-webapi/2008Mar/0095.html

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