I’ve fixed the typo, and regarding your comment on “to leak or not”, I have come to the habit of never using the activation object for variables that need be accessed inside inner functions. In this case, neither f nor n can be DOM objects agreed (as they are supposed to be a function and an integer respectively), but if I for the fun of it (and for the errors it will throw) invoke it with n set to some DOM object, that I remove from the DOM afterwards, we might get a leak quite easily (not tested though).

Thus I have come to the habit of never using the activation object in such smaller helper functions, that are generalized to work on just about anything.

Interesting to see different approaches. I won’t get into a debate about global functions, but I should point out that use of closures do not cause memory leaks. Memory leaks tend to be caused by circular references between JavaScript objects and DOM objects — closures can make such references hard to spot, but they do not cause the leaks. This has nothing to do with the DOM, in fact I’ve just been running my method millions of times through Drip and it shows constant memory usage.