Huh? You don't HAVE to use always on/ always off. Just enable Firebug on the sites you want to use it on by clicking the bug. On sites you don't want to use it on, don't click the bug.
-- Josh -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of nroussi Sent: Friday, August 14, 2009 12:42 PM To: Firebug Subject: Re: Firebug 1.4 - A step backwards? I have been using Firebug for a very long time and this version forced me to install Opera with dragonfly. I design and develop pages and I want to be able to disable it for specific sites like gmail and also enable it for specific sites (like the ones I am working on). This always on/always off is a really bad idea. If it was done to save memory then I guess the developers of Firebug forgot who their target audience is. Dont get me wrong, I appreciate a free product and I appreciate the work behind firebug. It is a shame though to not be able to use it anymore. If there is anyone that installed firebug 1.3 on Firefox 3.5 please let me know as I dont want to use Opera. Regards On Aug 14, 10:07 am, johnjbarton <[email protected]> wrote: > On Aug 14, 2:11 am, dan_m2k <[email protected]> wrote: > > > I'd agree. Though the latest build has solved a lot of the problems > > that I've found of late, the lagest Firebug does feel like it's fallen > > backwards - the activation model being one of the main bugbares. > > > The firebug icon (colored/greyed out) is counter intuitive as it often > > fails to respond to the 'enable all panels' or 'no panels' options - > > therfore giving no meaningful feedback, and likewise there is no > > If you can help us reproduce this we can fix it. > > > intuitive way to find out you've accidentally enabled for everything, > > until, say, you find that gMail has issues loading as it's going thru > > Firebug. > > Any suggestions? I'm not sure what you mean by "accidentally". Do you > mean "I set On for All Web Page" then forgot I had set it because the > UI does not change when this option is set? > > > > > The various other issues relating to console logging being hit and > > miss, the inspector failing to highlight the selected node/failing to > > keep it selected, and the net tab, make the end user experience very > > frustraiting. > > Of course we can't fix these problems. > > > A side note to other users - I did have some performance improvements/ > > less glitches by completely removing Firefox and all application > > support, library folders and so-forth from my Mac before doing a > > reinstall of FF and Firebug. YMMV. > > I strongly discourage users from uninstalling Firefox to fix Firebug > problems, it almost never works. The reason is simple: the problems > are almost always in the Firefox configuration settings ('profile') > and uninstalling or reinstalling does not change these settings. > > The most effective way to reset your browser is to create a new > Firefox profile. > > jjb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
