Comments on: Using Opera to troubleshoot Javascript errors in IE http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html Why accept things as-is when you can tweak them with a little code? Wed, 10 Mar 2010 16:19:59 +0000 http://wordpress.org/?v=2.0.2 by: Ivan http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-9052 Wed, 28 Jan 2009 21:00:00 +0000 http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-9052 Well, I'm using JS debugger for IE, the one from MS Office. It's not as cool as, for example, firebug in firefox (firebug is the best web-developing tool I ever seen), but it's pretty useful for JS debugging. Breakpoints, variables, tracing, it really can do it. As for extending of error description, maybe Opera console is better, I'm not sure. Without normal debugging tool it's very poor, and advices "add [postError] after every JS line" is very, very annoying (maybe even idiotic). Nowdays Opera is proudly introduces Dragonfly, on fact - firebug clone. But it's still alpha or so, it's somewhat loading from Opera site (sic), and many of it's features works strangely. Summary: use firebug for developing/debugging wherever you can. For specific browser errors there must be debugging tools in the every browser. For IE it can be installed from MS Office (used on 99% windows comps, Vis studio hmmm.. 5% ?). For Opera wait for stable Dragonfly or buy debugging app (he-he-he) or shamanic dances. Well, I’m using JS debugger for IE, the one from MS Office. It’s not as cool as, for example, firebug in firefox (firebug is the best web-developing tool I ever seen), but it’s pretty useful for JS debugging. Breakpoints, variables, tracing, it really can do it. As for extending of error description, maybe Opera console is better, I’m not sure. Without normal debugging tool it’s very poor, and advices “add [postError] after every JS line” is very, very annoying (maybe even idiotic). Nowdays Opera is proudly introduces Dragonfly, on fact - firebug clone. But it’s still alpha or so, it’s somewhat loading from Opera site (sic), and many of it’s features works strangely.
Summary: use firebug for developing/debugging wherever you can.
For specific browser errors there must be debugging tools in the every browser. For IE it can be installed from MS Office (used on 99% windows comps, Vis studio hmmm.. 5% ?). For Opera wait for stable Dragonfly or buy debugging app (he-he-he) or shamanic dances.

]]> by: Yanal-Yves http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-9050 Sun, 25 Jan 2009 23:59:34 +0000 http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-9050 Hello, No money is needed : Visual Studio Express Edition is free (this is not a trial but a free version of Visual studio) - http://www.microsoft.com/express/vwd/ As an alternative way you may also use Microsoft script debugger : http://www.microsoft.com/downloads/details.aspx?familyid=2F465BE0-94FD-4569-B3C4-DFFDF19CCD99&displaylang=en Hello,

No money is needed : Visual Studio Express Edition is free (this is not a trial but a free version of Visual studio)
- http://www.microsoft.com/express/vwd/

As an alternative way you may also use Microsoft script debugger : http://www.microsoft.com/downloads/details.aspx?familyid=2F465BE0-94FD-4569-B3C4-DFFDF19CCD99&displaylang=en

]]> by: Yanal-Yves http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-9049 Sat, 17 Jan 2009 21:28:08 +0000 http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-9049 Use Visual Studio Express Edition : it's free ! http://www.microsoft.com/express/download/ Use Visual Studio Express Edition : it’s free !

http://www.microsoft.com/express/download/

]]> by: vlad http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-8152 Thu, 24 Apr 2008 13:39:14 +0000 http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-8152 Hi! I just wanted to say that I've tried DebugBar and IEWatch - the new nifty tools made my M$ to bridge the infinite gap between them and web developers, and they both suck. I cannot use them for simple error reporting in JS. I can use Opera though, and I thank you for this blog post! Seeing it was written 2 years ago, I shiver. M$ still sucks, and I do not doubt that IE8 will too. PS. The VS2008 solution is hilarious... I mean.. AS IF! :PP - though I don't doubt it's effectiveness. Oh, if someone tries this, please use a pirated copy :) Hi!
I just wanted to say that I’ve tried DebugBar and IEWatch - the new nifty tools made my M$ to bridge the infinite gap between them and web developers, and they both suck. I cannot use them for simple error reporting in JS.

I can use Opera though, and I thank you for this blog post!

Seeing it was written 2 years ago, I shiver. M$ still sucks, and I do not doubt that IE8 will too.

PS. The VS2008 solution is hilarious… I mean.. AS IF! :PP - though I don’t doubt it’s effectiveness. Oh, if someone tries this, please use a pirated copy :)

]]> by: 110110010 http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-7655 Tue, 11 Mar 2008 07:59:48 +0000 http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-7655 Hey! You didn't help me a lot.. I've got an error in big script, but only IE says there's an error. Opera and Mozzila Firefox run the script without any bugs... So what should I do, if I haven't got any money to buy Visual Studio? ... Hey! You didn’t help me a lot.. I’ve got an error in big script, but only IE says there’s an error. Opera and Mozzila Firefox run the script without any bugs… So what should I do, if I haven’t got any money to buy Visual Studio? …

]]> by: Yanal-Yves http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-6320 Sat, 12 Jan 2008 12:51:07 +0000 http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-6320 In order to debug javascript under Internet Explorer, install Visual Studio 2008, create a new web site, put your hmtl/javascript app inside. On IE menu "Tools"=>"Advance Option" under the "advance" tab clear both "disable script debugging" checkboxes and check "display a notification about every script error". In VS2008 run the website in debug. You will be able to debug everything on a web page (breakpoints, watch, wiew all scripts loaded by a page, ...etc! Debuggin IE will never be the same! In order to debug javascript under Internet Explorer, install Visual Studio 2008, create a new web site, put your hmtl/javascript app inside. On IE menu “Tools”=>”Advance Option” under the “advance” tab clear both “disable script debugging” checkboxes and check “display a notification about every script error”. In VS2008 run the website in debug. You will be able to debug everything on a web page (breakpoints, watch, wiew all scripts loaded by a page, …etc! Debuggin IE will never be the same!

]]> by: Chrsi Dawes http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-6277 Fri, 11 Jan 2008 04:07:25 +0000 http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-6277 debug bar (debugbar.com) is great for IE and free for personal use! :-) debug bar (debugbar.com) is great for IE and free for personal use! :-)

]]> by: HL http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-4560 Tue, 06 Nov 2007 19:43:18 +0000 http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-4560 As much of a pain it is to get the DOM working with IE, I really can't hate its debugger; it not only allows you to break and step through javascript, but also allows you to read its call stack and the contents of all objects within the scope of the breaking function. As much of a pain it is to get the DOM working with IE, I really can’t hate its debugger; it not only allows you to break and step through javascript, but also allows you to read its call stack and the contents of all objects within the scope of the breaking function.

]]> by: Steve Love http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-146 Sat, 31 Mar 2007 07:05:29 +0000 http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-146 Thank you! You just saved me a whole heap of trouble trying to figure out what Internet Explorer meant exactly when it told me an object was expected. Thank you! You just saved me a whole heap of trouble trying to figure out what Internet Explorer meant exactly when it told me an object was expected.

]]> by: netdragon http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-139 Tue, 06 Mar 2007 16:56:14 +0000 http://thecodegirl.org/index.php/2006/07/05/troubleshooting-javascript-errors-in-ie.html#comment-139 Opera doesn't use IE's Javascript engine, so although I think Opera tries to mimick the way IE works to some degree on some things, it will only give false positives as to what the problem is in other cases. I'd instead focus on trying to make it also work in Opera, and hope that solves the problems in IE. If not, I'd use MS's script debugger (or Visual Studio). I know it stinks, but 'tis life. Someday, hopefully, Microsoft will get their acts together. Opera doesn’t use IE’s Javascript engine, so although I think Opera tries to mimick the way IE works to some degree on some things, it will only give false positives as to what the problem is in other cases. I’d instead focus on trying to make it also work in Opera, and hope that solves the problems in IE. If not, I’d use MS’s script debugger (or Visual Studio). I know it stinks, but ’tis life. Someday, hopefully, Microsoft will get their acts together.

]]>