[finally put my finger on the actual issue...] 1. jbarton says, "If you had ever done this in the past for that URL, Firebug would already be active."
I think that's the issue right there. Firebug remembers URLs, not domains. When I'm developing, I'm developing on a domain, not a URL. I am working on a web application and every time I go to a new resource (with a new ID), I have to re-enable FB. Any time I move to a different controller (base url)... have to re-enable FB. That's why I couldn't figure out what it was doing -- this behavior is so counter-intuitive to my workflow it didn't even cross my mind that FB would be activating based on specific URLs. This is not the kind of thing that should be fixed with a plugin -- this is bread and butter workflow for most of us. Some of you (who work for large companies with names that start with G or Y) may not be working on applications that span entire domains, but most of us are. 2. The other issue is the X button. I'm sure I'll get used to it eventually, but there's some big cognitive dissonance going on with the X (close) button and the Firebug icon. I know now that clicking the X _disables_ fb, and clicking the bug icon just hides it. But that was not immediately apparent, and I'm having a hard time teaching myself the new behavior. I have the feeling that we expect the opposite to be true -- clicking the bug enables FB, so clicking the bug again would disable it, right? [nope]. And the X says to me, "close this interface", not, "disable firebug". But this is a minor issue compared with #1. Hope this is helpful. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to firebug@googlegroups.com To unsubscribe from this group, send email to firebug+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
