Unfortunately the UI changes surrounding activation have created a lot of confusion!
Following Honza's advice, it is clear to me now what the Firebug team were intending. However, all this negative feedback is tantamount to a UAT fail. I think people found it much more intuitive to right click the Firebug icon in the status bar to turn on/off for a given window. Now we have a multitude of options, including panel activation / all-window control, none of which seem to work as hoped. After all this pain and suffering, I just had to click "off", which unfortunately is in the same place as the old "close Firebug panel" (if memory serves) which did not deactivate Firebug! For anyone having the same issue, pop out Firebug and open up a few tabs. Then use the "off" icon in the top right to disable specific windows. Overall, this is just seems confusing given the way Firebug used to work. I vote for a return to simpler activation control. Paul PS: Kudos to the dev team nonetheless, they work tirelessly. But please understand this is causing real user pain! On Sep 8, 4:37 am, Jan Odvarko <[email protected]> wrote: > > The new versions of Firebug it's buggy sometimes and I don't like at > > all the modifications. > > I don't like that I must mantain the firebug window open to view the > > Console requests > > made, it was much better before! > > If you want to have the window closed, but still collecting all XHRs - > just minimize it using a minimize button "_". When you close Firebug's > UI using "x" (Off) button, Firebug is deactivated. > > > Besides, I'd like to see only the GET/ > > POST requests, > > not all the long image/js/etc. requests, it's very annoying. > > I don't understand what you mean by this. The Console panel displays > only XHRs. All requests (like image, js, css, etc.) are displayed in > the Net panel, where you can filter it using toolbar buttons. > > > I don't understand the message: "Reload to activate window console". > > But the console > > it's activated, how does it sounds? > > If you open Firebug it misses the page load phase where all listeners > are registered (e.g. this is why you don't see anything it the Net > panel). You have to reload to allow Firebug to hook into the page. If > you close the page with Firebug being open, it'll be opened > automatically the next time you load the page so, you don't need to > reload. > > > I really want to have Firefox 3.0/3.5 having the old versions which > > seems to be better. > > This is a general opinion from all my devlopement team, please > > consider this! > > Please, tryhttp://getfirebug.com/releases/firebug/1.5X/firebug-1.5X.0a23.xpi > + alsohttp://getfirebug.com/releases/firestarter/1.5/fireStarter-0.1.a3.xpi > > We have fixed some problems (also related to Firefox bug) and the > activation is more stable. > > The Firestarter extension implements "Activate By Default" option > (Firebug is active for every page automatically and you can switch it > of for specific pages by clicking on the "x" (Off) button. > > It also allows to log sites for which Firebug is de/activated into the > (Firebug) Console panel. See status bar context menu. > > Honza --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
