Hi John, thanks for the reply. I read through the blog post, but I'm no closer to finding a good solution for working with the new model -- only that it will cause slow-downs in my normal workflow (and from reading other topics, it's obviously caused a lot of frustrations from others over the same issue).
In the previous model, it was possible to enable Firebug only for the domains I needed it enabled for, all other browsing of websites was not affected. It remained closed while active on that domain so that it could catch any firebug logging or errors that would occur. While browsing the domains I am working on development for, if an error crops up, I catch it, I don't have to remember to turn Firebug on for my session, or enable it for all web pages, which takes a huge hit on the performance. If I forget to enable Firebug, I could miss these errors. In the old model, clicking the (x) hide your panel, now it deactivates the panel and you have to go through all the steps required to reactivate your settings. It's not intuitive that (x) means disable Firebug. And especially since that exact button did something completely different in Firebug 1.3 that everybody got used to. You don’t have to please everybody by appeasing the 'vast majority', but it would seem to me that if you have a vast number of users, each of whom have a different preference, that control over that preference should be paramount. 1.4 has simply taken the control away from the users over how they wish Firebug to be active and enabled. If it were not for the speed of Firefox 3.5 and Firebug 1.4, I would switch back to Firefox 3.0 just so I could have the old activation model back. In the various topics on this discussion forum, there are 4 topics full of disappointed users with the new activation model. Of the responses in those topics including the feedback topic, 72% of the users either hated or were disappointed with the new model. 12% liked the new model, and 16% were indifferent. I'm really hoping Firebug will go back to the old model, or have some kind of combination between the two models because I understand why it was changed, but I do not think it was a good change for a lot of people. - I would really hate to have to install a plugin to get the desired functionality that already existed in a previous version. There may also be bugs here that are causing much of the annoyance as well. E.g.: when you enable firebug, your subsequent pageload (not refresh) will usually load with Firebug disabled, and clicking on the Firebug icon is required to activate Firebug again, at which time it will remain active. Shutting down Firebug, the subsequent page load will not only reactivate Firebug, but open the Firebug window as well. Requiring you to shut it down a second time. The third thing is the (x) causing Firebug to shut down unexpectedly for all the users who were used to the functionality of Firebug 1.3 Thanks again for your time and work on Firebug. :) - Highway of Life Software Engineer --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
