I really like how the new activation scheme works. It is much simpler than the 1.3 model (which I really didn't like at all).
I would just like it to: 1. always activate when I visit a particular page where I previously _opened_ it (as it currently does) 2. stay active for the duration of that tab without flagging any other pages which visit as pages for which it should open 3. don't unflag pages that I happen to come across unless I close the panel while on them and they were flagged Brade wrote: > Completely agree with sir_brizz and will hughes. This new "activation > model" is patently insane and just made my life 100 times more > difficult. If someone were to create a fork of Firebug 1.3 that > preserved domain whitelisting/blacklisting, I would pay $50 for it > easily. johnjbarton, since you seem oblivious to how the new version > is problematic, let me spell out some common scenarios I have tried: > > Previously I enabled firebug for localhost, since that's where I do > most of my testing and developing. Then I would browse from page to > page (without the panel open) until the "script error" message came up > on the status bar. Then I'd open the firebug panel and troubleshoot. > I'd fix it then perhaps browse around a few more pages, with the panel > still open. When I was happy I'd solved the problem, I minimized > firebug (back in those halcyon days, I could click the "x" button or > the little firebug icon to remove the panel--it didn't matter). But > firebug stayed active, so I would be alerted to script errors if they > happened. > > Fast forward to today. Seems firebug now remembers panel position PER > PAGE, which is ludicrously stupid. So as I browse from one page to the > next, the panel is randomly disappearing and reappearing. And of > course I can no longer simply tell firebug to be active only for > localhost. WOW, WHAT SOME GREAT NEW FEATURES, GUYS! > > The new system is completely absurd, and I hope now you can begin to > see why. When a tool as ubiquitous as firebug gets changed so > drastically, the question is WHY? We all loved it before, so please > stop butchering it. And again, I put out the call to some developer > out there who would want to continue the awesomeness of firebug 1.3 > and perhaps rename it. That person would be regarded as a hero at this > point... > > --brad g. > > > On May 10, 11:46 pm, Will Hughes <[email protected]> wrote: > >> I've been using1.4.0a27 and the release immediately prior (I don't >> remember the version, sorry), and I have to say that the activation >> model is driving me absolutely batty. >> >> I often use Firebug to debug webservice calls, and having the Firebug >> Networkpanelnot capture activity because I've opened a new tab or >> window is incredibly frustrating. >> >> I need a setting *somewhere* (even if not in the UI) so that I can >> force the Networkpanelto activate always on certain sites or >> globally - I don't particularly mind either way. >> >> I really really love the JSON decoding, but the current model has >> (cumulatively) lost me more hours than if I had stayed with 1.3 and >> decoded the results manually. >> >> On Apr 2, 3:27 pm, John J Barton <[email protected]> wrote: >> >> >>> Firebug1.4a16 is available fromhttp://getfirebug.com/releases/firebug/1.4X. >>> We are getting close to beta. >>> >>> One of the issues we need feedback on is the new activation model. Of >>> special importance are ideas for how to support use models that suffer >>> in the new scheme without adding options to the UI. >>> >>> 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 -~----------~----~----~----~------~----~------~--~---
