John -- I'll work on producing a test case as soon as I can, and attach it to a bug report. It also occurs to me that this problem could be due to a change in ff 3.0.1, too. I wish I could remember exactly when breakpoints were working for me.
I am experiencing the problem while debugging a project with huge amounts (above 1MB, uncompressed, unminified) of JavaScript, so that may trigger the problem, too. Thanks also for all your hard work on Firebug -- as soon as we get this one figured out, Fbug can once again be my main debugging tool! - G On Sep 19, 9:26 am, John J Barton <[EMAIL PROTECTED]> wrote: > On Sep 18, 11:52 pm, Francois Piat <[EMAIL PROTECTED]> wrote: > > > Hello, > > I have encoutered a problem with breakpoint too, but not really the > > same as the one discussed here. > > When I put breakpoints and remove them they are still active in every > > popup opened (FF2 & 3, FB 1.2.1) > > There are no bug reports on breakpoints. I'd fix them if you produce > a test case where I can see the problem. > > > > > I must say that I not very happy with this new release of FireBug > > (console.log error, slower treatments, ...) > > If you use FF2, issue window.loadFirebugConsole() before > console.log(). We had no choice: the console had to be reimplemented. > > What is a "treatment"? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
