> Work on Firebug 1.4 is complete. Your scenario description is a good > one, I wish we had it back when we were working on this feature. I'd > love for Firebug to be perfect for everyone, but in every change there > will be some winners and losers I guess.
This is exactly why the design shouldn't be considered closed when you go into beta. Any major and disruptive workflow change like this needs the benefit of *as much user input as possible*, even if it *is* the major improvement you believe it to be. Also, I have yet to understand who exactly the winners are - especially since you haven't given any compelling reason for *removing* domain filtering. Sure, a more fluid and dynamic way to activate Firebug seems nice, especially for new users, but it also seems completely orthogonal to being able to say "just activate everything always for this site." > The activation model in 1.4 was designed to allow extensions to > provide special activation solutions. If anyone wants to create one > for this use case we'd be happy to give advice. (Just to set > expectations, I have no plans to do any more work on activation > myself). Will those extensions allow for as convenient an interface to domain filtering as 1.3 had? Being able to activate a tab permanently for the current domain was quick and easy before; are we now going to have to dig into a separate extension preferences dialog if a plugin implements it? - Luke --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
