I guess it turns out that Trevan's use case is the only one that seems broken now.
IMO, when Firebug is *not showing* it needs to keep not showing, regardless of what the previous tab/page state was. The behavior in 1.3 was that Firebug stayed in the same state whether monitoring the page or not between pages and tabs. It seems nonsensical to have Firebug act as if the panel is open on the previous tab/page when it was not open at all. Considering Trevan's use case, the Firebug panel is minimized, then shown, then turned off (and thus minimized), then un-minimized for seemingly no reason. Following this same case, if I went to a page, opened Firebug to check out some HTML, then clicked Off and then went back to another page that was whitelisted, Firebug panel would show. How can you make the Panel stay minimized on all whitelisted pages by default? That is the question here. If you only want Firebug panel to open when requested on a page, you can't have that happen given the use case provided in Trevan's post. Mine seems to have gone away since 1.4b8. On Jul 28, 10:07 pm, johnjbarton <[email protected]> wrote: > Thanks for the careful and clear instructions. > > On Jul 28, 2:53 pm, Trevan Richins <[email protected]> wrote: > > > If you modify those steps to: > > > 1. Open getfirebug.com > > 2. open firebug (UI is visible), > > 3. reload. Firebug is debugging the page. > > 4. Minimize Firebug > > 5. New tab,http://groups.google.com/group/firebug > > 6. Open firebug > > At this step you opened Firebug, that is you set its placement to in- > browser. From this point forward until you minimize or detach the > placement will be in-browser. > > > 7. Close firebug with the Off button > > Well you deactivated Firebug for the web page. I can see now why you > think that you also changed the placement. > > First there is the UI: it now looks the same as minimized. > Second there is the experience from 1.3, where the same motion results > in minimize. > > > 8. Switch back to the tab from step 4. > > > Firebug is now opened. > > Right, using the placement which has not changed since step 6: in- > browser. > > > > > Though I thought this was an already known bug. > > Not only not a 'bug', but also not known as an issue. That is, no one > wrote down that sequence and explained what they expected. > > I don't see a clear simple solution. Causing Off to also Minimize > will but just as confusing to other users I guess. > > A clearer UI for minimize, that is very or at least clearly different > from suspended (where you end up after Off) would help. > > 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 -~----------~----~----~----~------~----~------~--~---
