You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It traps the exception and relies on the toString() method to be properly implemented in the console.
In IE, you get "Uncaught exception in [Object]..." which isn't all that helpful.
Disabling this method and actually throwing the exception on the other hand provides useful info even in IE.
Remind me again why we need this exception trapping in the first place? :)
The text was updated successfully, but these errors were encountered:
We run through calling a bunch of methods in a row, and if one of the first methods throws an exception, we often need to still call later methods (i.e. to isolate namespaces)
If you get an exception in an event handler (especially in onmatches) and you don't catch exceptions they are silently swallowed.
Better solution would be to get exceptions printing properly in IE. Must be a library around that does pretty printing.
Thanks for the explanation! Pretty printing still won't allow the console to use its built-in features around linking objects and DOMElements to its own interactive views, right? Even just a stack trace would be better than nothing though :)
Why would we need to call later methods once one fails? I'm happy for an exception to halt JS execution.
It traps the exception and relies on the toString() method to be properly implemented in the console.
In IE, you get "Uncaught exception in [Object]..." which isn't all that helpful.
Disabling this method and actually throwing the exception on the other hand provides useful info even in IE.
Remind me again why we need this exception trapping in the first place? :)
The text was updated successfully, but these errors were encountered: