Opened 12 years ago

Closed 12 years ago

#2952 closed defect (duplicate)

[Firebug] Firebug in IE is eating errors, preventing debugging.

Reported by: haysmark Owned by: anonymous
Priority: high Milestone: 0.9beta
Component: General Version: 0.9
Keywords: Cc: haysmark@…
Blocked By: Blocking:

Description

While the Firebug console in IE does display all of the console.log stuff, it eats all of the actual errors (you know, the ones we are trying to debug?) The Microsoft Script Debugger does not interrupt execution like it normally does, telling me that there is a bad try/catch somewhere in Firebug that prevents the Script Debugger from noticing anything.

Debugging with this Firebug for IE is impossible. You can't set breakpoints, you can't evaluate statements, and it can't step into eval code like in the Script Debugger.

Ironically, I've got around this problem by turning debugging OFF. This disables the silly Firebug for IE console and allows errors to pass through to the real Script Debugger, where I can actually do something about the errors.

I love Firebug+Fireclipse upgrade for Firefox, but this Firebug for IE is nothing close to that combination. We shouldn't have to turn debugging off in our test files to debug in IE. Get a Firebug that works please, or remove it entirely.

Change History (2)

comment:1 Changed 12 years ago by bill

Component: WidgetsGeneral
Owner: changed from bill to anonymous
Priority: highestnormal
severity: blockernormal

I'll reassign to alex since this has nothing to do with me. But I'd suggest using MSE97.exe rather than "Microsoft Script Debugger". It's much better. See http://dojo.jot.com/DebuggingJavascript

comment:2 Changed 12 years ago by alex

Resolution: duplicate
Status: newclosed

haysmark: you've conflated several related by separate issues. I've taken a look at firebug.js and it's not squelching. We've also taken care to ensure that other exception handlers in Base are at least logging. As a result, I'm closing this in favor of http://trac.dojotoolkit.org/ticket/3583 and marking it a dupe.

Note: See TracTickets for help on using tickets.