- From: <bugzilla@jessica.w3.org>
- Date: Sun, 24 Aug 2014 00:08:47 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25412
--- Comment #26 from Arkadiusz Michalski (Spirit) <crimsteam@gmail.com> ---
Reopened because IE11 and Chrome36 allow recursion but support them in other
way. Small test case with only NodeIterator and NodeIterator.nextNode().
<div id="box">
<p>First P.</p>
<P>Second P.</p>
<P>Third P.</P>
<hr>
</div>
<script>
var root = document.getElementById("box");
var i = 0;
var iterator = document.createNodeIterator(root, NodeFilter.SHOW_ELEMENT,
function(node){
i++;
if (i < 4){
(function(i){
var node = iterator.nextNode();
document.write("iterator.nextNode(): " + node);
document.write("<br>");
document.write("iterator.nextNode().textContent: " +
node.textContent);
document.write("<br>");
document.write(i);
document.write("<br><br>");
})(i);
}
return NodeFilter.FILTER_ACCEPT;
}, false);
document.write("init: " + iterator.nextNode());
</script>
Results:
- IE iterate by all (root and P);
- Chrome stuck on root;
Maybe its only bug in Chrome and allow recursion can stay in DOM, or maybe
dissallow this completly (like was before).
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 24 August 2014 00:08:50 UTC