[Bug 28107] TreeWalker nextNode never ascends the tree

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28107

--- Comment #4 from Bergi <a.d.bergi@web.de> ---
Let's take the following tree:

html
 body
  div
   p
   p
  div

(which is also the tree order from top to bottom).
If we now create a TreeWalker on `body` (accepting any element nodes),
* the first `nextNode()` call will set the current node to the first `div`
(substep 1, subsubstep 3)
* the second `nextNode()` call will set the current node to the first `p` (same
steps)
* the third `nextNode()` call will not go into substep 1, as the `p` has no
child. In substep 2 it checks whether there's a node following the current node
(both the second `p` and second `div` match this), and whether that node is
**not following root** - but both of the candidates do follow `body`! So `null`
is returned and the tree walker stops.

So the phrase "not following root" needs to be replaced by "is a
[descendant](https://dom.spec.whatwg.org/#concept-tree-descendant) of root".

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 22 August 2016 17:32:29 UTC