I've created an <a href="http://code.google.com/p/fbug/issues/detail? id=2135">issue #2135</a> for the problem.
On 28 июл, 15:50, "Alex Ryazanov AKA the Marrch Ca'at" <[email protected]> wrote: > After reading the topic and trying to make things clear (I experienced > the same difficultes as Winfield had), and trying to provide you with > specific test scenarios, I've finally found the solution instead!! > > Winfield, there is one thing you need to know to be almost happy with > FireBug 1.4. It isn't noted neither in docs nor in faq on the site - > or at least it isn't clear enough. The thing is: > When you've opened a FB panel on a tab, it automagically becomes > active for the site opened on that tab. If you don't need that, you > have to press the off button in the top-right corner of the panel, and > it will DISABLE firebug FOR THAT SITE ONLY. The firebug icon in > statusbar will become gray to indicate that. But it will still be > ACTIVE on all the tabs you need it to be active on, and the icon will > be orange on that tabs! > If you need to collapse the panel on any tab you need FB to be active > on, you just need to click the left of the three top-right icons, and > that will collapse the panel without disabling it. > > Well, then I'm ready to state two issues on the new firebug, one of > which I treat as a bug and another - as a big disadvantage. > > 1. When I expand or collapse the FB panel on any tab it's active, it's > really expanded and collapsed all over the FireFox (or at least all > over the FF window, if several windows are opend - I haven't checked > yet). That means that if I need to switch between two tabs, one of > which I had to see in full height (e.g. with FB collapsed) and the > other I needed with FB on (to monitor something), I have to click the > FB icon once and again and again and again and... Well, that's not a > problem, but it's really frustrating. I suppose that option to allow > FB remember the collapsed/expanded state of it's panel on each tab > separately - would be really wonderful for many developers using it. > > 2. When I collapse the FB panel, switch to another tab that FB isn't > active on and accidentally click on FB icon - FB becomes active and > expanded. It's not what I want, so I press the Off button, and it's > disabled and collapsed. But it doesn't treat that as collapsing > internally, so when I switch to a tab I have FB active on, it's > automagically expanded. It's a very unclear behavior, and I treat that > as a bug: if the paradigm is that FB is expanded/collapsed for the > whole app, not for a single tab, then when I collapse it on one tab it > should be collpased everywhere - despite the way I did that. > > Obviously, the root of both problems is the same: the new idea that FB > should be expanded/collapsed application-wide, not for a given tab. > I'm not sure that it's good for all FB users, and I'd supposed making > the behavior optional. I think there were internal reasons to do so, > but I don't think it'd be hard to remember one bit (expanded/ > collapsed) for each tab and to restore the expanded/collapsed state > when switching tab - if user wishes so. > > Sincerely yours, > Alex, the Marrch Ca'at. > > On 27 июл, 18:20, Winfield <[email protected]> wrote: > > > > > I've been using Firebug actively for several years in web development > > and I'm very pleased with the FireBug <= v 1.3 behavior (global on vs. > > global off w/ WhiteList enablement). It takes a short time to add all > > of the sites I actively develop on (local dev system, staging, > > production, etc) and FireBug immediately is enabled only for the > > places I want it. Adding new hostnames to the list is straight- > > forward and easy. > > > I upgrade to FireFox 3.5 and firebug 1.4 earlier this week and found > > the new Enablement system very confusing. My main use-case is to open > > and close Firebug repeatedly while it captures JavaScript and Network > > information, especially JavaScript errors. > > > However, Firebug's new "automatic" behavior disables Firebug every > > time I hide the Firebug pane or switch tabs which usually prevents me > > from being able to use it again (for example, code that prints to the > > JS console breaks when the console is repeatedly enabled/disabled by > > the automatic system). > > > I understand the motivations in trying to simplify the configuration > > and code required for "manual" enable/disable in 1.3 and prior > > versions, but the new 1.4 system is frustrating and unusable for me. > > I had to downgrade my development system to FireFox 3.0 and Firebug > > 1.3 to meet any of my normal development needs. > > > I'm sorry to see the vocal anger and disrespectful feedback being left > > on the groups here. I completely echo that sentiment. I waited 4-5 > > days to cool off from how angry/frustrated using Firebug 1.4 made me > > to try and be civil. > > > Please reconsider this new feature!- Скрыть цитируемый текст - > > - Показать цитируемый текст - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
