On Sep 8, 4:20 pm, crunchyt <[email protected]> wrote:
> Thank you for your suggestions! I am happily using 1.5X0a23 without
> issue. :D
>
Thanks, that's good to hear.
> The removal of "Off for all Web Pages" was a good move. Also, my
> previously
> stated issue with "Enable/Disable All Panels" is no longer relevant
> now the menu
> options are clear.
>
> However, in older versions of Firebug, the docked panel could show
> without
> Firebug being activated. This still seems clearer to me. It meant
> users could click
> the FBg icon without activating FBg.
And they still can to this, just disable all of the panels.
>
> Here is a typical "I didn't read the manual" scenario:
> 1. User installs FBg
> 2. User clicks the icon (activating FBg)
> 3. User decides s/he doesn"t want to use Fbg and clicks the icon to
> close it again (common behaviour for snap-in UI elements)
I guess you mean the firebug status bar icon.
> 4. User sees the Fbg icon is not grayed out, and starts searching for
> a way to "disable" just this window
> 5. User shrieks in frustration (like me!) because it isn't apparent
> that the OFF icon does more than just closing the panel
I can't see how to win this one. If the OFF button is moved to the
status bar context menu, then it is hard for new users to find and it
takes two clicks for experienced users.
>
> Admittedly, some users may click the OFF button in step 3. However,
> since most people who use FBg are developers with some experience,
> they will probably be lazy (like me!) and simply click the Fbg icon a
> second time to close it.
But as far as I know the Firebug statusbar icon has always minimized
Firebug.
>
> I applaud the recent fixes, and the FireStarter extension. However,
> you are creating a need to read a manual / go searching for answers,
> whereas in previous versions it was immediately apparent how to enable/
> disable a given panel when docked.
Apparent for you perhaps, but not for everyone. It seems some users
find one way better than another.
>
> Cheers
> Paul
>
> On Sep 8, 5:18 pm, Jan Odvarko <[email protected]> wrote:
>
> > > The use of check boxes for the "On for all pages" / "Off for all
> > > pages" is confusing. I am able to toggle
> > > off both of them, or use the"Off" selection to disable the "On"
> > > selection. All the while, I still can"t seem
> > > to selectively disable Firebug for certain windows (e.g. Gmail,
> > > etc...)
> > > Firstly, please consider removing the redundant option, and let the
> > > checkbox do what it is deisgned for.
>
> > We decided to change this.
>
> > > Secondly, is it possible to selectively enable/disable Firebug for
> > > certain tabs like it used to be?
>
> > - Keep Firebug active for a site, it'll be activated automatically the
> > next time (white listing).
> > - Deactivate Firebug for a site (using the Off button), it'll be
> > deactivated the next time (black listing)
>
> > You can also log white/black lists into the console using
> > FireStarterhttp://getfirebug.com/releases/firestarter/1.5/fireStarter-0.1.a3.xpi
>
> > > I'm running on FB 1.4.2 on FF 3.5.2. I tried a clean install with no
> > > other plugins, but was unable to turn off
> > > Firebug in selected tabs/windows without disabling it in every tab/
> > > window.
> > > Is this problem any better in 1.5a?
>
> > Yes. Notice that we made a workaround for a Fx
> > bughttps://bugzilla.mozilla.org/show_bug.cgi?id=510984
> > so, the behavior is more stable. We are also thinking about
> > backporting this into 1.4.
>
> > Honza
>
> > > Cheers
> > > Paul
>
> > > On Sep 1, 3:38 pm, johnjbarton <[email protected]> wrote:
>
> > > > On Aug 31, 4:10 pm, allholy1 <[email protected]> wrote:
>
> > > > > >> I liked the old way of doing it so much better when it was a
> > > > > >> checkbox
> > > > > >> or whatever and you could choose to enable firebug always on a
> > > > > >> certain
> > > > > >> site you where at. It was simple and it worked.
> > > > > >I suggest you try Firebug without the On For All Web Pages if you
> > > > > >want
> > > > > >it on for some and off for some.
>
> > > > > He could do this, but upon refresh of the page at hand, firebug is
> > > > > turned off, disallowing testing of javascript calls upon pageload. I
>
> > > > As a description of how Firebug 1.4 works, this statement is
> > > > incorrect. If it describes your experience with Firebug 1.4, then you
> > > > probably have a problem in your installation. I suggest you try
> > > > Firebug 1.5a22,http://getfirebug.com/releases, in case you are one of
> > > > the unlucky ones who always have trouble with 1.4.
>
> > > > > feel that this might be better if you set it to be on for a website,
> > > > > then it stays on even though the page is refreshed.
>
> > > > I am uncertain what you mean by "on for a website". If you are
> > > > suggesting "On for All Web Pages", I repeat that this option is
> > > > designed only for users who really really want Firebug on for every
> > > > single web page at all times.
>
> > > > jjb
>
> > > > > Nick
>
> > > > > On Aug 29, 5:37 pm, johnjbarton <[email protected]> wrote:
>
> > > > > > On Aug 29, 2:12 pm, chobo3 <[email protected]> wrote:
>
> > > > > > > Hi
>
> > > > > > > I have the l firebug 1.4.2 and I set it to be turned on, on all
> > > > > > > sites.
> > > > > > > When I go to a site that I don't want firebug to run so I turn it
> > > > > > > off
> > > > > > > for those sites. It however does not work it always turns it back
> > > > > > > on.
> > > > > > > Like I will hit refresh on the same page and it will load up
> > > > > > > firebug
> > > > > > > even though I told it to be turned off.
>
> > > > > > Yes, because you said "On for all Sites". If you don't want it on
> > > > > > for
> > > > > > all sites, don't use that option.
>
> > > > > > > I liked the old way of doing it so much better when it was a
> > > > > > > checkbox
> > > > > > > or whatever and you could choose to enable firebug always on a
> > > > > > > certain
> > > > > > > site you where at. It was simple and it worked.
>
> > > > > > I suggest you try Firebug without the On For All Web Pages if you
> > > > > > want
> > > > > > it on for some and off for some.
>
> > > > > > > I actually think the older versions of firebug where alot better.
> > > > > > > I
> > > > > > > found the last couple versions the UI keeps changing and I to
> > > > > > > figure
> > > > > > > out where everything is and I find changing stuff like this just
> > > > > > > seems
> > > > > > > to make things worse. The old way seemed simpler and it worked.
>
> > > > > > You can try Firebug 1.5a22. Some users have a mysterious problem
> > > > > > with
> > > > > > the pageAnnotation service we use for page activation in 1.4. That
> > > > > > was
> > > > > > changed in 1.5.
>
> > > > > > > I have no clue why this does not work. Does cookies need to be
> > > > > > > enabled?
>
> > > > > > No, you just need to take off the option "On for all pages". Then
> > > > > > Firebug won't be on for all pages.
>
> > > > > > 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
-~----------~----~----~----~------~----~------~--~---
