firebug console swallows dojo.lang.declared class method thrown exception

[guest]

Kind of a weird one...

Firefox 1.5 and Firefox 2.0 using Firebug 1.05. Confirmed on both Windows & Linux.

I dojo.lang.declare a class Foo with a method bar() that throws a new TypeError?. I then instantiate foo and invoke foo.bar from Firebug's console. Firebug swallows the TypeError? silently instead of displaying the TypeError? in the console as expected.

I've been in contact with the Firebug folks, and we can't reproduce this using regular Javascript OOP practices. Check out the complete thread ​http://groups.google.com/group/firebug/browse_thread/thread/613cbc91dba58422.

[guest]

Recreate using dojo-0.4.3 off AOL's CDN

[Adam Peller]

Show bug, sans Dojo

[Adam Peller]

A little unfair to blame Dojo on this one. Prototype should fall into the realm of "regular JavaScript? OOP practice" Works fine in Drosera :) I'd chalk it up to another jsd mystery. See attached.

Thanks for forcing me to look at this, though. I think it explains a LOT of times I couldn't find exceptions in Firebug.

[guest]

Thank you for your time on this one. I've taken the dojo-less recreate back to the Firebug folks ​http://groups.google.com/group/firebug/browse_thread/thread/613cbc91dba58422.

[guest]

No change to the defect, just a related hint...

It looks like Firebug 1.05 will show the error if you open up Firefox's [about:config] page and set extensions.firebug.showChromeErrors to true. The capability exists but isn't presented by the Firebug UI as of 1.05.