> 1) The activation logic should cover only main use cases (those we > understood from all the feedback) that are typical for Firebug users.
But this IS the common use case: We have a site of our own that we're debugging. We want Firebug up all the time for that site and never for others. We're not just whining about something we were used to; this is actually a worse design for the common cases. BTW, what *is* the use case for the new activation model? AFAICT, it's only more convenient if you frequently decide to debug arbitrary sites out of sheer curiosity, and want to be sure you can easily switch it on and off per-tab because you only want to debug *one* arbitrary site while you surf others. I'm certainly sympathetic to tinkering, but favoring an odd use case that only makes sense for casual fiddling over the more common one that may have professionals using Firebug for hours each day simply makes little sense. Besides, even if tinkering *is* such a compelling use case, is it really so overwhelmingly so that it's worth *eliminating* the functionality far better suited to debugging a single site? Firebug is a development tool, and now you've hamstrung its usability as a tool used for focused development. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
