It's that I don't understand this feature and, since it will be invisible, I think it can be a trap for users. For example, consider the "break on errors" feature. People select it, they break on the error, they love it. They go off and fix the error. The next day Firebug is broken. It keeps breakpointing all over the place. That's because they forgot the invisible break on error option was set.
But let's go back the "why minimize always". Is the reason for this feature like this: "I don't mind Firebug's overhead, I'm good with it being active all the time, every page, just in case I want to debug a page"? jjb On May 4, 9:14 pm, Hernan Rodriguez Colmeiro <[email protected]> wrote: > On Mon, May 4, 2009 at 16:54, johnjbarton <[email protected]> wrote: > > Currently minimized pages are not restored minimized. The problem here > > is that if you open firebug, minimize Firebug, exit the page, then > > some time later you revisit the page what should happen. We could > > restore minimized. But then the user would easily forget that they had > > Firebug on for the page. I don't like these kinds of hidden surprises. > > Couldn't this be configured by some kind of setting? If there's "On > for all web pages" why not "Minimized for all web pages"? > You may say this can clutter the UI, and you're probably right. But it > would be nice to have this option, at least in about:config, while we > search for a good alternative in the UI ;) > > Hernán --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
