I agree with this. The button that minimizes Firebug should be the upper right-most icon.
On Jul 6, 11:47 am, Nicolas Hatier <[email protected]> wrote: > I would think so, but would probably better if the [Off] button would be > at the left of all buttons, and the [_] button would be where the [X] > button currently is: > > [Off] [some space] [8] [_] > or (to keep the normal order of buttons, maybe) > [Off] [some space] [_] [8] > > Of course, this is just my opinion, I'm don't have an argument for or > against a particular button order, except that the button hiding the > Firebug UI (minimize) should be the rightmost. > > Regards > NH > > johnjbarton wrote: > > So this problem would be resolved if the [X] button was removed and a > > new button at the same location appeared with a label like [Off] and a > > tool tip saying "Deactivate Firebug for this site"? > > > I want some thing on the primary UI for deactivation. > > > jjb > > > On Jul 6, 9:40 am, Nicolas Hatier <[email protected]> wrote: > > >> As written by many people before me, the [x] button deactivating Firebug > >> is not intuitive. We are aware that a X button on an external window > >> closes that window, and may close the application if it's the last > >> window. But the X button on a panel usually only closes that UI element, > >> not the service/application behind it. > > >> Just in Firefox, there is several examples of that: If you click the X > >> button on the History panel, Firefox continues to remember you pages > >> history. If you have, say, the AdBlock Plus extension and close the > >> "blockable items" panel using its X button, AdBlock Plus continues to > >> run. There is many other examples. > > >> Of course, the same argument could work in the other direction - If I > >> click the X button of a Firefox tab, the tab is closed for good and the > >> page behind it is disappeared. > > >> My point is, the "right" (design-wise) thing to do when the X button is > >> clicked may or may not be to disable Firebug. But, given the amount of > >> feedback received yet, disabling Firebug is probably not the right thing > >> to do. We saw a lot of comments telling it's not OK, and a few comments > >> telling something along the lines of "I didn't expect that, but I can > >> get along with it". I didn't read any comment yet telling something like > >> "yay, I didn't understand why the 1.3 X buttn didn't disable Firebug"... > > >> For me, the X button doesn't do what it should, but I can get along with > >> it. I would probably prefer the minimize [_] button to be moved where > >> the X button currently is, and the X button removed, replaced by two > >> menu entries in the Firebug icon right-click menu: "Disable Firebug for > >> this page", and "Disable Firebug for this domain", which would simply > >> remove the annotations for the page or the domain. > > >> Regards > > >> NH > > >> johnjbarton wrote: > > >>> On Jul 6, 3:54 am, alfonsoml <[email protected]> wrote: > > >>>> On Jul 5, 7:29 pm, johnjbarton <[email protected]> wrote: > > >>>>> On Jul 5, 9:10 am, alfonsoml <[email protected]> wrote: > > >>>>>> An entry in the context menu of the firebug statusbar icon: > >>>>>> Disable Firebug for "xyz.com" > > >>>>> I gather you think that a hidden menu entry with text is better than a > >>>>> visible iconic button? Do others agree? Other choices? > > >>>>> jjb > > >>>> As sir_brizz says, previous versions linked the "close" button just to > >>>> the panel, not to the state of Firebug. > > >>> But here again you are proposing a solution where I don't see a > >>> problem. > > >>>> For me Firebug is a background task, it must be running always in > >>>> every page that I'm working on (based on domains, not on the exact > >>>> page url), and I might need to open or close the panel to view some > >>>> state, debug a function, etc.. but the panel is just the interface of > >>>> Firebug, the internal code that catches errors, keeps trace of network > >>>> resources is separate and shouldn't be linked together. If I enable > >>>> Firebug for a domain it should work automatically for every page of > >>>> that domain until I disable it, without the need to open the panel and > >>>> without disabling itself when I close the panel with the same button > >>>> that I've been doing since eons ago. > > >>> Ok there are two things I understand from this description. > > >>> First, 1.3 had a [X] that implemented minimize. So you are confused > >>> because 1.4 uses [X] for a different purpose. I totally forgot that > >>> 1.3 had an [X] button, I thought we added it new to 1.4. > > >>> Second, I'm now in a jam because I need a two icons one for > >>> "deactivate" (1.4 uses [X]) and one for minimize (1.4 uses [_]). > > >>> I hope you can understand why I can't just change the [X] button to > >>> implement minimize. Then I don't have a button for deactivate and I > >>> have two buttons that both implement minimize right next to each > >>> other. > > >>> 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 -~----------~----~----~----~------~----~------~--~---
