@johnjbarton -

I hope to take some time to configure a FireFox 3.5/FB 1.4 system
again and pursue some of the issues you raised.

It sounds like some of the behavior is configuration/upgrade problem
that may be fixed by creating a new FireFox profile.

I also understand your frustration with high-level critiques that are
not delivered with clear scenarios/examples of step-by-step behavior.

There is very little as frustrating as a developer than to build a new
feature/improvement and have users misunderstand/dislike it when you
feel it's genuinely valuable.  I hope that those of us who are
frustrated and unhappy with the new enablement config can explain to
you on your terms why we feel this way.

FireBug is by far the most powerful and useful development/debugging
tool available to me, which is why I feel so strongly.

@alex/marrch -

Thanks for digging deeper into this!  We can't be the only ones who
are confused/frustrated with this.

As of now it's much easier to downgrade to FF3.0/FB1.3 than to spend
time figuring this out.

On Jul 27, 12:02 pm, johnjbarton <[email protected]> wrote:
> On Jul 27, 7:20 am, 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.
>
> The same team that wrote 1.3 wrote 1.4 and we have the same goal:
> excellent results for all Firebug users.
>
>
>
> > 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.
>
> We need a lot more detail than this.  By open/close I guess you mean:
> "show/hide" the Firebug UI? It is very helpful if you list the
> specific steps in terms of the Firebug UI buttons, not words like
> "close" which can have multiple meanings.
>
> The most common problem with 1.4 has been the replacement of the [X]
> icon. The upper right corner icon "[U] Off" turns firebug off. The [_]
> icon or a second click on the Firebug status bar icon minimizes.
> seehttp://blog.getfirebug.com/2009/07/15/minimizing-firebug-1-4/
>
>
>
> > 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).
>
> The 1.4 mechanism is not more or less "automatic" than the 1.3 system.
> I do not think it is helpful to categorize the actions that 1.4 takes
> in some derogatory way ('automatic', "smart', etc). That only detracts
> from focusing on the real question of how to make Firebug work well
> for you.
>
> So if you give specific steps and what results happened that you did
> or did not expect, may be we can sort it out.
>
> Note that if you change to a tab where you have not requested Firebug
> to be active, then the entire Firebug engine suspends and the Firebug
> icon goes gray. That is the only way we can support the mix of debug
> and non-debug uses of Firebug on the same Firefox window.
>
>
>
> > 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.
>
> Thank You!
>
>
>
> > Please reconsider this new feature!
>
> I don't know what feature you are having problems with; I don't yet
> know if your problem is only in your system, due to our poor
> documentation, or is a real use case problem with 1.4.
>
> jjb
>
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to