What would you expect to be the result of executing the following code?
// Create a medium size array, at least 100 items var obj = []; for(var j=0, k=150; j<k; j++) { // the value here doesn't matter. obj.push('ABCD'+j); } // Sort the array alphabetically. obj.sort(function(m,p){ m=(''+m).toLowerCase(); p=(''+p).toLowerCase(); if(m > p) return 1; if(m < p) return -1; return 0; });
The obj Array should now be sorted, in alphabetical order based on value. BUT, in our best friend Internet Explorer, a Number Expected error may be the result. Don’t be fooled if your test array behaves correctly, it only happens intermittently for arrays of varying size!
So, I whipped up a quick test to check the damage. Iterating over array sizes from 1 to 150, running the Array sort algorithm. The following failures resulted:
| Browser | Failures * |
|---|---|
| Internet Explorer 6 | 4 sizes out of 150 |
| Internet Explorer 7 | 18 sizes out of 150 |
| Internet Explorer 8 (and Compatibility Mode) | 2 sizes out of 150 |
* Failures may vary to the specifications of the test machine.
Of course, the Number Expected error is going to result whenever your code doesn’t return a number inside of the function callback. But the problem here is something deeper than simple application code failure. The problem is in JScript itself. Any modification to the sort arguments may result in the Number Expected error.
m=(''+m).toLowerCase(); // modifies the argument m and is unreliable.
This problem will manifest itself more frequently if you use the Google Closure Compiler, which restructures JavaScript to reuse argument variables if possible, probably to save the 4 character penalty of a “var ” declaration.
Normally, reusing argument variables is a safe practice for primitives, since they are passed by value and not by reference, as is the case in this Array sort example 1. So, what exactly is going on here? One commenter at the Google Closure Compiler bug seems to think that the actual array values are being passed by reference instead of by value. I’m not completely convinced that’s the case.
The Fix
Don’t reuse the argument variables inside of an Array sort function.
// Changing the above example obj.sort(function(m1,p1){ var m=(''+m1).toLowerCase(), p=(''+p1).toLowerCase(); if(m > p) return 1; if(m < p) return -1; return 0; });
Check the source code of the demo file to see the different methods of modifying the arguments that I attempted.
- If you want to learn more about passing by value or reference, Jonathan Snook has a nice explanation.
Internet Explorer can’t make you do anything, it can only make you wish you hadn’t.

Subscribe
Follow

10 Comments
Nice write-up. I wonder if your suggestion can be incorporated into the compiled code Google Closure compiler outputs. I noticed that the same solution (of not reassigning the argument variables) fixes the issue in IE for the problem that led me to post that ticket.
I don’t see why they wouldn’t incorporate it, since it is introducing bugs in all versions of Internet Explorer. We’ll see how your report pans out. I’ve submitted a bug before to the Closure Compiler team and it was fixed right away.
Thanks for this. I got my sort function working in IE8 because of this. Otherwise, it was only working in Firefox and Google Chrome.
IE 9 Preview seems to be fine, ran the test several times with no failures.
New blog post: Internet Explorer Array.sort Unreliable http://www.zachleat.com/web/2010/02/24/array-sort/
This comment was originally posted on Twitter
JavaScripts reusing the argument variables inside of an Array.sort() function are unreliable in IE: http://is.gd/99VIr
This comment was originally posted on Twitter
RT @zachleat: New blog post: Internet Explorer Array.sort Unreliable http://www.zachleat.com/web/2010/02/24/array-sort/
This comment was originally posted on Twitter
RT @zachleat: New blog post: Internet Explorer Array.sort Unreliable http://www.zachleat.com/web/2010/02/24/array-sort/
This comment was originally posted on Twitter
Don’t modify Array.sort args. IE breaks. http://bit.ly/aj9LGr via @zachleat
This comment was originally posted on Twitter
RT @ls_n: Don’t modify Array.sort args. IE breaks. http://bit.ly/aj9LGr via @zachleat
This comment was originally posted on Twitter
One Trackback
[...] Internet Explorer Array.sort Unreliable – като стана дума за лоши технологии, IE има проблем с Array.sort. [...]