Using Opera to troubleshoot Javascript errors in IE
Wednesday, July 5th, 2006I have a web app that uses a bunch of to do Ajaxy things as well as simple hide/show of DIVs. None of it seems to work in Internet Explorer. Since I am forced to support this horrific “browser”, I figured I better check every page within IE. IE error messsages regarding javascript suck. Like IE, they are completely utterly USELESS. Most of my error messages are a simple ‘object expected’. Wow, thanks for nothing.
I decided to give the same web app a try in Opera just to see how it behaved. Unfortunately it breaks in almost all the same parts. Bonus: the Opera Javascript console is infinitely more helpful and specific with its error messages.
Example:
Event thread: click
Error:
name: ReferenceError
message: Statement on line 1: Reference to undefined variable: showFilterOptions
Backtrace:
Line 1 of script
showFilterOptions();
return false;
At unknown location
Why the %^&* can’t IE give out that kind of info? The “script debugger” I got from MSDN was also of little use troubleshooting, and sucked up a lot of ram/cpu cycles.
Bottom line: use Opera’s javascript console to debug any javascript issues that Internet Exploder is having.
EDIT: I use Linux for my desktop and development. I can run IE thanks to WINE. However I wouldn’t even consider attempting to run additional Windoze software. Therefore Opera’s debugger is the best choice _for me, as a Linux user_. But YMMV



