Ok so here is how break on Errors works. The Firefox engine javascript debug API (jsd) has a function "onError" that is called for all Javascript errors. If the Firebug implementation of this function returns 'true', that's it, the js processing continues. If Firebug returns "false", then Firefox jsd is supposed to call "onDebug" next. Break on Errors is a flag that causes Firebug's implementation of onError to return 'false'.
When I trace the execution of Firebug 1.4 on FF 3.1b3 for the referenced page with BreakOnErrors true, I see the messages from onError, but not from onDebug. So apparently FF goes wander off rather than calling us back. The Firebug text case for Error processing also fails FF3.1b4; it also prints messages from onError then stops. (I was tempted to use onError/onDebug to improve Firebug's error reporting. onError does not know what window triggered it (oy), but onDebug does. So the combo would allow Firebug to more correctly report at least javascript errors. Unfortunately exceptions that are caught also pass through this code). jjb On Apr 19, 9:32 pm, johnjbarton <[email protected]> wrote: > For me: > On WinXP FF 3.0.8, break on errors works on that page. > On WnXP FF 3.1b3, FF stops responding. > > jjb > > On Apr 19, 10:43 am, Steven Roussey <[email protected]> wrote: > > > Forgot example: > > >http://demo.swfupload.org/v220/applicationdemo/index.php > > > On Apr 19, 10:38 am, Steven Roussey <[email protected]> wrote: > > > > Am I the only one that sees this corrupt all of Firefox (on every > > > try). I've even see it black out the chrome sometimes. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
