The question here isn't what should happen when you go to a new tab. The "on for all pages" means Firebug should be on.
The question is what should the [X] do when "On for all pages " is true. Probably it should be disabled. After all the UI promised "on for all pages", not "on for all but ones you click the [X]" Does that make sense? I think the clarity of the 1.3 model is partly because most people actually did not understand it. If you set the panels enabled once and focused on the site controls, then you probably were lucky. Else not: the 1.3 model coupled the panel activation, site activation, and placement (detached, minimized, in browser) So if you start changing these other settings you can get mixed up pretty quick. The 1.4 model is much clearer. The activation, placement, and panel enablement are all separate. If you notice in all of these discussions we did not once get into panel enable/disable. That was a huge issue in 1.3. The placement part of the UI (the [_] [-][X] controls) was added later in the design and we have less feedback on them. I do not think we have all of the UI for these prefect by any means, but its also just not that bad. jjb On Jul 2, 5:00 pm, sir_brizz <[email protected]> wrote: > Perhaps. > > 1) Are you suggesting that Firebug should keep a blacklist of disabled > sites when "On for all sites" is checked? Currently it doesn't, I > believe that is the correct behavior. > > 2) In the case where "On for all pages" is checked, the meaning of > "Close" and "Minimize" blurs almost entirely. Close could just mean > "get out of my way" as much as minimize could. > > Anyway, I believe the appropriate behavior should be that the panel is > up on the following page only if it was up on the page previous. If > the panel is not showing for any reason on the originating page, it > should not pop up on the resulting page, either. This is certainly one > of those cases I was talking about before when I said that "How should > [some process] function?" question is way too easy to bring up with > the new activation model. In 1.3, or with an even more flexible > whitelist/blacklist model, there would simply be no question what > should happen in this case. > > On Jul 2, 5:54 pm, johnjbarton <[email protected]> wrote: > > > On Jul 2, 3:07 pm, sir_brizz <[email protected]> wrote: > > ... > > > > You're right, this is the correct use-case: > > > > 1) Right click Firebug, check "On for all pages". > > > 2) CLOSE Firebug (with the 'x'). > > > That would be "Deactivate FIrebug for this page" ;-) > > > > 3) Open a new tab > > > -- Firebug panel pops open instead of staying minimized. > > > It wasn't minimized so it won't stay minimized. It was deactivated on > > a page, then the tab obeys "On for all pages". > > > 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 -~----------~----~----~----~------~----~------~--~---
