> I don't understand the connection between enabling/disabling and > location. This sounds like a bug to me, please give step by step > instructions in terms of the button labels in the UI to reproduce your > problem.
I don't think it's a bug. I didn't describe it clearly. I am on site A and I inspect element. I then click to another tab to see site B. Now my firebug which was opened in new window no longer shows me the HTML tree of site A, which is what I want to see while I am looking at site B. > > There are other use cases for me also, for which this new schema does > > You need to be specific. We can't guess based on "other". As others have noted, the issue of having to reload to reload to activate window console. This is not convenient, for me at least, meaning it slows me down in my work. > What page are you referring to? In any case, we are not interested in > solutions that fail for 20% of the users, you must be misinterpreting > our message. That could be. I can't now find that page. It was a response to a comment on a Firebug blog somewhere which I understood to say that the Firebug team realizes that some people will find the new system not as useful while others will find it more useful. It mentioned that 80% were expected to like it and 20% would not. That's what I recall anyhow. Thank you. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
