SitePoint Sponsor

User Tag List

Results 1 to 5 of 5
  1. #1
    SitePoint Enthusiast
    Join Date
    Oct 2005
    Posts
    32
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    IE Debugging - the phantom menace.

    Hello,

    I have been happily working away with Firebug developing up a webpage to put on the interpipe. I fire up IE7 every now and then to check things are looking ok (is it just me or is the antialiasing pretty poor?). My web 2.0 app (working fine in FF) has gotten pretty large by now, and when IE gives me the old:

    Line: <random number>
    Char: 1
    Error: you have made an error
    Code: 0

    It makes me want to cry. My question is, how do you guys debug in IE? Do you have any tips or advice? I know there are paid-for solutions like http://www.ieinspector.com/dominspector/index.html, but is there anything free out there? Thanks a lot.

    PS I called this thread "the phantom menace" because IE debugging is, like the Phantom Menace, crap.

  2. #2
    SitePoint Guru
    Join Date
    Apr 2006
    Posts
    802
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Micosoft script debugger- you may have it installed already, if you have any MS Office programs, or it is a free download from Microsoft.
    Or the IE developer tools.

    There is also an IE script debugger, but I never had any luck with it.

  3. #3
    CSS & JS/DOM Adept bronze trophy
    Join Date
    Mar 2005
    Location
    USA
    Posts
    5,482
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I recommend you download these two free tools:
    Microsoft Script Debugger
    Internet Explorer Developer Toolbar
    We miss you, Dan Schulz.
    Learn CSS. | X/HTML Validator | CSS validator
    Dynamic Site Solutions
    Code for Firefox, Chrome, Safari, & Opera, then add fixes for IE, not vice versa.

  4. #4
    SitePoint Enthusiast
    Join Date
    Oct 2005
    Posts
    32
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Thanks a lot guys!

    I installed both the debugger and the developer toolbar. I found the bug which was a trailing comment in an object - Mozilla is more lenient about this.

    Nice one, IE debugging is slightly better now, bringing it up to "Attack of the Clones" level.

  5. #5
    SitePoint Enthusiast
    Join Date
    Feb 2004
    Location
    Third Stone From The Sun
    Posts
    82
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    The Phantom of the Park is no joke.

    Use the Microsoft Script Editor.

    If you have a lot of files, you can try deleting the ones that don't have dependencies. If the error goes away, you know it is in one of those files.

    Look for the trailing comma. If you see:

    foo = {
    a : 1,
    };

    you have to change that for IE.
    My outdated site is down for a while now.


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •