• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Wrestling with MSIE

 
author and iconoclast
Posts: 24207
46
Mac OS X Eclipse IDE Chrome
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm relatively new to serious JavaScript, being in the middle of my first largish application right now. I'm finding, as I think many people have before me, that coding for Firefox and debugging with Firebug is a joy, but then if I test on IE and find that things don't work, it can be agonizing to figure out why.

I've tried the "Microsoft Script Debugger" and found it truly wretched -- it usually hangs stepping around XmlHttpRequest calls, for example, and generally misbehaves in many other ways. Surely there must be something better? How do you figure out where IE is going wrong?
 
author
Posts: 15385
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You can infect your machine with Visual Studio!

Eric
 
Sheriff
Posts: 67748
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have no good news for you.

My version of IE6 will not even show debugging errors, regardless of what the Advanced settigns are configure to.

It's dreadful.
 
Ranch Hand
Posts: 15304
6
Mac OS X IntelliJ IDE Chrome
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The only advice I can give is to use try/catch EVERYWHERE. Especially around ajax calls and there completing function(s). Then you can actually spit out semi-meaningful messages:



Versus the good old "Warning: Object expected null Line 1" crap.
 
Eric Pascarello
author
Posts: 15385
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
IF you are WILLING to infect your machine you can install Visual Web Developer Express

http://asp.net/downloads/essential.aspx?tabid=62

You add a debugger; statement to the code and it will allow you to use it. I use Visual Studio to debug things, but I normally go the classic alert model.

Eric
 
Ranch Hand
Posts: 48
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You might try this:

http://www.getfirebug.com/lite.html

I have yet to try it myself, but it has got to be better than the alternatives.

Chris
 
reply
    Bookmark Topic Watch Topic
  • New Topic