I just ran into this issue last night. The problem: I had a loop that was adding a callback to a method. Something like this:
for(var i=0;i<10;i++){
$myElement.on('some-event', function(){
DoSomethingWith(i);
});
}
What I expected was that the value of the i variable at the time it was called would be used in my callback method. However, this was not the case… the i variable was the same in every single callback.
See this JSFiddle for an example.
The reason for this? JavaScript variable hoisting. Before your code is executed it is scanned and the variables are processed. This has the effect of moving your variables to the top of the current function regardless of where in the function they are defined. (Except for in cases where you are implicitly declaring global variables).
So, in our situation we’ve defined var i. This is processed before the loop is processed and it is as if we wrote this:
var i;
for(i=0;i<10;i++){
$myElement.on('some-event', function(){
DoSomethingWith(i);
});
}
Now it becomes a bit more clear why we are running into the issue with i being the same. The reason is because by the time the callback is executed the for loop has already run and the value of the i variable is already 10.
The solution, as far as I can tell, is to use an IIFE to scope the variable correctly in order store the current value for later. It looks ugly and it feels hacky… but it seems to be what is necessary. Update: It appears that you can also use .bind to set the value correctly as well.
var i;
for(i=0;i<10;i++){
$myElement.on('some-event',
(function(i){
return function(){
DoSomethingWith(i);
};
})(i);
);
}
And the JSFiddle to demonstrate.
Example With .bind
var i;
for(i=0;i<10;i++){
$myElement.on('some-event', DoSomethingWith.bind(undefined, i));
}
