Ditto here, I don't want it on for all pages either. I work with Typo3 (a CMS) and hate having firebug open with the interface, yet I need it open for the pages I am working with. Its irritating.
On Jun 30, 11:42 am, MorningZ <[email protected]> wrote: > But i don't want "on for all web pages" (i assume that's the option > you speak of) > > I only want it "on" for domains i specify, like 1.2 and 1.3 were... > > I'd really go back to those, but there's issues that 1.4 fixed that > are important > > On Jun 30, 12:21 pm, Trevan Richins <[email protected]> wrote: > > > You can make firebug always on (right-click the icon in the bottom bar). > > I've also been playing around with an extension for my own development that > > forces firebug to always be on for my development domain. I've got issues > > with it where it is minimized when it shouldn't be or maximized when it > > shouldn't be, and I've never tested "open innewwindow" but it is working > > fine for me. The email thread where I've asked questions about the > > extension is titled "Help with extension to enable Firebug at a specific > > domain". I could post my code and let you try and make it work for you. > > > Trevan > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] On Behalf > > Of MorningZ > > Sent: Tuesday, June 30, 2009 10:12 AM > > To: Firebug > > Subject: Re: I hate thenewdesign. > > > I'm going to chime in with another dislike of thenewdesign... it > > really is a pain > > > if i am on sitewww.mmm.com, i want Firebug active and watching what's > > going on... i don't want to worry if the Firebug panel is showing, > > "active for current tab" or anything, the like...... > > > what I do want is the ability to have it watching a given domain no > > matter what... because i want to see my full browser window and if > > there's an error or some AJAX call is taking too long, i want to be > > able to click the bug icon, see the panel and watch the request, not > > have to refresh the page and start over because i didn't have the > > panel pulled up... (1.3 was great with this) > > > this is a situation "if it ain't broke, don't fix it" > > > On Jun 30, 11:05 am, Kara Rawson <[email protected]> wrote: > > > johnjbarton wrote: > > > > We'd be interested in what problems you are encountering. Thedesign > > > > work for 1.4 is complete; we use beta just for bugs notdesign > > > > changes. Our goal is to make Firebug work well for as many users as > > > > possible. > > > > > jjb > > > > > On Jun 29, 3:39 pm, Dan <[email protected]> wrote: > > > > >> Dear Firebug, > > > >> Please do not keep thedesignin the latest beta. It is messing up all > > > >> my habits and is constantly wasting my time. > > > > >> Thanks, > > > > at first i didn't like thenewdesign, but it grew on me, only took a > > > few mins to get used to it. I use both, as i used FF3.5 with the latest > > > FB and FF3.1 with the older stable release of FB. using both side by > > > side, thenewversion actually is alot easier to use, its just a little > > > difference, IMHO a better flowing, UI. I also agree with spending more > > > time on getting it to work well with as few bugs as possible. > > > > k --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
