Background:
I came across a very strange phenomenon while working with a node list. I wanted to use getElementsByClassName or something similar and then sort it. I decided one way would be to iterate through the nodelist and push each item to an array and sort the array. (This did work by the way but not as expected). I tried using the for (var i in nodeList) to iterate through, but it kept throwing an exception on the last few items, which were undefined. the weird part is I could instead use for (var i = 0; i < nodeList.length; i++) to iterate through. I just tested it again and on a stackoverflow page I ran in my console the following code:
for (var i in document.getElementsByTagName("span"))
console.count("items");
console.log(document.getElementsByTagName("span").length);
It counted out to items: 382 but length gave 380. As expected, when I entered document.getElementsByTagName("span")[380] and document.getElementsByTagName("span")[381] they came back undefined. This strange behavior does not occur on arrays (granted, nodeLists and arrays are different, but this does prove that it’s not the different for loops causing the issue).
question:
Why does for(var i in nodeList) constructs behave differently on nodeLists returning a couple of undefined items at the end?
The two additional properties that the
for initeration statement catches are:Let me give you a simple example. Let’s say that there are 3 SPAN elements on the page.
Now,
spansis a NodeList object which contains 5 properties:The first 3 properties are indexes and they contain references to those SPAN elements. The other two properties – length and item – are two additional properties. All NodeList objects have these two properties.
The
for instatement iterates over all 5 properties of the NodeList object, which is probably not what you want. Therefore, use a regularforstatement.