My git commit for this afternoon, following 3 hours of debugging and work, contained the following description:
IE7 fixes. DAMN that browser is busted.
Hello? I'd like to see what the error is, and where it's happening. By default, all that IE gives you is the Gray Box of Doom that tells you the problem is on line 24696, but won't tell you which file it's referring to.
Microsoft Script Debugger is the only standalone tool available, and it's no longer supported by MS. The other options require installation of either Front Page or Visual Studio. Puh-lease.
Firebug is free for Firefox. Open source 2, Microsoft 0.
Array.forEach() doesn't work? That's been around since Ecmascript 1.6! That's right, IE7 still doesn't implement any of the crafty Array iterator methods.
Just. Effing. Boggling.
At the end of all that, which quite frankly made me more dumb than when I started, I found myself asking the question: "Can I get away without supporting IE in my product?"
The realistic answer is obvious, but doesn't the fact that I'm asking the question in the first place tell you that something is seriously busticated?
The details behind the Pit of Despair Known As Internet Explorer have been covered in way more detail (and by more knowledgable people) than I can hope to do. I'm just adding my voice to the chorus of "WTF?"s that are already out there.