I've been using Firebug actively for several years in web development and I'm very pleased with the FireBug <= v 1.3 behavior (global on vs. global off w/ WhiteList enablement). It takes a short time to add all of the sites I actively develop on (local dev system, staging, production, etc) and FireBug immediately is enabled only for the places I want it. Adding new hostnames to the list is straight- forward and easy.
I upgrade to FireFox 3.5 and firebug 1.4 earlier this week and found the new Enablement system very confusing. My main use-case is to open and close Firebug repeatedly while it captures JavaScript and Network information, especially JavaScript errors. However, Firebug's new "automatic" behavior disables Firebug every time I hide the Firebug pane or switch tabs which usually prevents me from being able to use it again (for example, code that prints to the JS console breaks when the console is repeatedly enabled/disabled by the automatic system). I understand the motivations in trying to simplify the configuration and code required for "manual" enable/disable in 1.3 and prior versions, but the new 1.4 system is frustrating and unusable for me. I had to downgrade my development system to FireFox 3.0 and Firebug 1.3 to meet any of my normal development needs. I'm sorry to see the vocal anger and disrespectful feedback being left on the groups here. I completely echo that sentiment. I waited 4-5 days to cool off from how angry/frustrated using Firebug 1.4 made me to try and be civil. Please reconsider this new feature! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
