I've complained about Firefox errors and especially about XULElement permission errors, I've never seen one that made any sense to me.
I suppose we could have a scheme where Firebug stops on errors but auto-continues on given error messages. jjb On Jan 2, 5:49 pm, magixman <[email protected]> wrote: > Understood. Just wishful thinking I suppose. For repeatable errors > your outline works brilliantly but for the one-off errors in a complex > applications the break on error is pure gold. I guess the real issue > is why I keep getting these stupid XULElement permission errors > because I have a mouse event over a scroll bar. Firefox is a great > environment for debugging cross-browser applications (mainly because > of Firebug) but still has a few rough edges. I can live with that. > > On Dec 22 2008, 12:34 pm, John J Barton <[email protected]> > wrote: > > > Theoretically you can > > 1) run your app, > > 2) get errors in Console > > 3) click on the error in the console to set a breakpoint > > 4) rerun and break on that error only. > > > I don't see how to implement "break only on errors that are not > > caught". The only way to know that an error is not caught is to wait > > for it to pass all of the catch blocks, at which point the execution > > is long past the point of the error. > > > jjb > > > On Dec 22, 9:23 am, magixman <[email protected]> wrote: > > > > Thanks John but the section you mention is for breakpoints and this is > > > a break on error. Basically I can't use use the break on all errors > > > because it breaks on normal errors in a try/catch block which happens > > > too often. It would be really nice if there was an option to not > > > break when in a try/catch block. > > > > On Oct 31, 1:34 pm, John J Barton <[email protected]> wrote: > > > > > Please try error breakpoints, seehttp://getfirebug.com/js.html > > > > The part that starts: > > > > Pause execution, but only if... > > > > > Let us know if that works for you. > > > > > On Oct 31, 9:04 am,magixman<[email protected]> wrote: > > > > > > Is there any way to have Firebug *not* stop on errors in a try/catch > > > > > but stop on all other errors? There is a "track throw catch" on the > > > > > options menu but this does not have an effect on whether it stops > > > > > within a throw/catch. > > > > > > There are a couple of weird buts in Firefox such as getting an > > > > > XULElement permissions exception when examining the thumb node that is > > > > > passed in from the onmouseout handler. This is easily handled with a > > > > > try/catch but unfortunately when using firebug it hits the error > > > > > everytime I hover over the scroll thumb. Another example is the > > > > > typical try/catch code when dealing with XMLHTTPRequest. > > > > > > Tried this on 1.2 and 1.3 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
