No. It is the fact that Firebug does not know what state it was on when you left a page, so it assumes that the default state for "On" is also "Panel open".
Just follow the steps Trevan posted, or follow this similar use case. 1) Clear the activation list. 2) Go to getfirebug.com and enable Firebug by clicking on the bug (added to whitelist). 3) Minimize Firebug 4) Open a new tab and close the previous tab. 5) Go to www.google.com and notice that the bug is grey (not active) 6) Go to getfirebug.com and notice that Firebug opens the Firebug panel because Firebug is active on this page. (The expected and desired functionality is that the panel stays minimized and just monitors this page until you need it) Because of the way previous versions of Firebug worked, if Firebug was minimized *it always stayed minimized*. It didn't care about being active or inactive, the panel being open was completely separate from that action, so if Firebug was disabled on google.com and I went to getfirebug.com where it was enabled in 1.3, Firebug panel would stay minimized. This is the "issue" I mentioned to you a week or so ago where I said that if you turn off firebug (which also "minimizes" the panel), it should stay minimized until you take an action to open the panel again, regardless of if the ensuing pages are on the whitelist or not. On Jul 28, 3:55 pm, johnjbarton <[email protected]> wrote: > Well I hate to disappoint you but we don't know how to do the scenario > I outlined. It certainly was not what 1.3 supported because the gray > firebug means exactly that there is no background activity. Otherwise > you can't read your gmail. > > Or to say it differently: there is no background/foreground. There is > only Firebug is active or suspended. You can't have Firebug suspended > on one page and active on another. Its not about the UI, its how > Firebug works. > > You *can* get firebug to have activity on tabs you are not looking at. > Just open Firebug on all the tabs, so the Firebug icon stays orange. > > Is that what all that talk about conflating visibility and activation > was about? That would explain why I found the discussion puzzling. > > jjb > > On Jul 28, 2:43 pm, Winfield <[email protected]> wrote: > > > I don't want to speak for nod, but this is EXACTLY what I am hoping > > for with this activation plugin. Hoping to check this out later > > tonight. > > > On Jul 28, 4:56 pm, johnjbarton <[email protected]> wrote: > > > > On Jul 28, 10:59 am, nod <[email protected]> wrote: > > > ... > > > > > Will we be seeing an option for what I will attempt to describe as: > > > > "auto-start and run Firebug minimized for whitelist URLs"? > > > > (Here I'm attempting to name/summarize the problem that so many people > > > > are writing about regarding wanting Firebug to "just STAY on darnit" > > > > for their whitelist so they never have to think about activation > > > > again, just as they didn't have to in <=1.3. Also known as > > > > "conflation of visibility and activation" and "have to reload page & > > > > reproduce to catch logging" and a few other descriptions.) > > > > Can you explain what you think "so many people" want? I can't figure > > > it out. > > > > How is "auto-start and run Firebug minimized for whitelist URLs" any > > > different from "minimize"? I mean if you minimize, then the page is > > > whitelisted and firebug is running. > > > > Does anyone have a test case where Firebug 1.4 does not stay on for a > > > page they have whitelisted? > > > > The only thing I can guess that matches what you describe here is the > > > following scenario: > > > > 1. Open getfirebug.com > > > 2. open firebug (UI is visible), > > > 3. reload. Firebug is debugging the page. > > > 4. New tab,http://groups.google.com/group/firebug > > > 5. Don't open Firebug. Firebug is gray. > > > 6. Switch back to the tab with getfirebug.com. Discover that all > > > console logging and ajax traffic has been ignored while I read the > > > newsgroup. > > > > Is that the scenario? Other wise I still don't get what you are > > > saying. > > > > 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 -~----------~----~----~----~------~----~------~--~---
