Here are some exceptions I see (even with new profile). I usually get them when I use debugger; to stop JS at some line, then wait for 5 minutes, then Refresh-browser(while Firebug is still holding/ controlling JS). And once I hit these exceptions, the only way to get- around is to completely-close firefox and reopen.
Exception #1. Firebug cannot find _firebugConsole element true Window #1 Exception #2. uncaught exception: _FirebugCommandLine init failed in http://rr.zimbra.com:7070/zimbra/#1 because TypeError: window.loadFirebugConsole is not a function There is one more exception that I know appears and I will update when I hit it. On Aug 2, 10:46 am, goodtest <[email protected]> wrote: > I have tried using new profile, but it didn't help much. Also, going > by bug count doesnt really help. How many *major* issues and *major* > annoyances would help. > > Anyway, here are the specific issues: > 1. If one of the object is null or undefined, it won't complain - BIG > issue. It only complain if we have "stop on all errors" turned ON. > 2. If we have "stop on all errors" turned ON, it shows the error right- > on-the-javascript-code. Its very hard to read whats wrong. > 3. Every now and then "New Watch Expression" stops working. i.e. > throws some NSException. I usually see this after I keep firebug > stopped at a debug-point for 5 minutes or so and then try to evaluate > some javascript expression. > > 4. Earlier, we could enable/disable firebug per website. This was > extremely helpful since, I didnt have to manually turn-off when I go > to yahoo.com, and turn-on when i go to myapplication.com. It was > automatic but currently, its very annoying I will have to remember > all the time. > 5. Because of 4, if we forget to turn-ON the debugger on > mypplication.com, and then say we realized that that and turn-ON > firebug, we still have to REFRESH browser for it to start working. > > On Aug 2, 8:06 am, johnjbarton <[email protected]> wrote: > > > First I'll say that we would not have released 1.4 if we had any > > evidence that 1.4 was too buggy to be useful. > > > "bugginess" is hard to measure, but if we go by the number of bug > > reports with test cases we'd have: > > 83 for v 1.2 or eariler (mostly 1.2) > > 29 for v 1.3 > > 72 for v 1.4 > > 184 total defects and enhancements with test cases, > > see:http://code.google.com/p/fbug/issues/list?can=2&q=label%3ATest-case-a... > > > Even though these numbers suggest 1.4 is 'buggier' than 1.3, I believe > > a large number of the 1.4 cases are dups or have been fixed by work we > > have completed. We have not had a chance to check for these. > > > Based on your list of problems, I would guess that your Firefox > > configuration is broken. If you install Firebug in a new Firefox > > profile, my bet is that these problems will all go away. > > Seehttp://groups.google.com/group/firebug/web/faq-about-firebug. > > > If this does not help, let us know. And if you want 1.3, all versions > > of Firebug are available athttp://getfirebug.com/releases. > > > jjb > > > On Aug 1, 10:40 pm, goodtest <[email protected]> wrote: > > > > I love-love-love firebug and use it every day. But every since Firefox > > > 3.5 and firebug 1.4 came up, its giving me headache. > > > - Doesn't keep itself ON > > > - Crashes every now and then > > > - Doesnt recognize Script errors > > > > Earlier versions were gem, and I don't know who came up with 1.4 > > > version. I want to go back to earlier 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 -~----------~----~----~----~------~----~------~--~---
