- From: <bugzilla@jessica.w3.org>
- Date: Thu, 26 Feb 2015 14:15:20 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28107
Bug ID: 28107
Summary: TreeWalker nextNode never ascends the tree
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: DOM
Assignee: annevk@annevk.nl
Reporter: a.d.bergi@web.de
QA Contact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, www-dom@w3.org
The https://dom.spec.whatwg.org/#dom-treewalker-nextnode algorithm seems wrong
to me. It only ever seems to descend to the first child of a node, or to its
sibling, but never returns to a higher level.
In contrast, its dual https://dom.spec.whatwg.org/#dom-treewalker-previousnode
does "Set node to its parent." when no more siblings are found.
This also would be consistent to the
http://www.w3.org/TR/DOM-Level-2-Traversal-Range/traversal.html#Traversal-TreeWalker-nextNode,
which says the method should "Moves the TreeWalker to the next visible node in
document order relative to the current node".
Btw, where did the
http://www.w3.org/TR/DOM-Level-2-Traversal-Range/traversal.html#Traversal-overview
sections go? They seemed quite helpful, what's the reason they were omitted
from the current spec?
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 26 February 2015 14:15:26 UTC