I don't see how either of those options are complex enough as to combat the utterly confusing functionality that is there right now. The problem is, the current 1.4 functionality *does not make sense*. And any expansions upon the current functionality only continue to make it not make sense.
I'm not sure how having a domain whitelist/blacklist is not preferable to the current system. Right now, it's difficult to even tell if Firebug is enabled/disabled or to get it to function properly once it has supposedly been enabled. It's important to note that I and many others raised this *exact same concern* several months ago when the activation model was being discussed. The current method is not only confusing but has multiple touchpoints where undesired behavior can occur. The old activation model was better in the sense that, if you wanted Firebug enabled a certain way, it wasn't hard to get it enabled that way. Then it was fire and forget. I'm not sure why a complex and confusing activation model was chosen over simpler methods because those simpler methods were considered too complex? o_O A little baffling there. On May 7, 5:56 pm, johnjbarton <[email protected]> wrote: > On May 7, 4:09 pm, sir_brizz <[email protected]> wrote: > > > I'm am COMPLETELY baffled about why so much effort is going into all > > these complex activation schemes when it seems like the easiest to > > develop and easiest to use functionality is already self evident. > > > One option "On by default with domain blacklist" or "Off by default > > with domain whitelist". > > We dropped that as too complex. > > > > > Then you either have Firebug always on (for those of us that just > > prefer to have it on by default on every page we visit) and a way to > > disable each piece of functionality per domain, or you have Firebug > > always off (for those that prefer the performance benefits) and a way > > to enable each piece of functionality per domain. > > Also dropped too complex. > > > > > Where did all this click, click, click to enable, disable, blabbity > > blabbity blabbity come from? 1.4 is completely confusing and > > incomprehensible right now. Previous versions of Firebug were very > > simple and minimalistic, they didn't require a bunch of knowledge > > about how the extension operated just to use it in a worthwhile way. > > I don't know what you are referring to. If you can list the steps that > you find difficult then may be I can comment. > > One problem with the discussion thread here is that it is a mix of bug > reports and learning how to explain the 1.4 mechanism. I believe the > final result will be simple enough. > > 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 -~----------~----~----~----~------~----~------~--~---
