On Jul 27, 7:20 am, HershelSR <[email protected]> wrote:
> I see there are comments on the project page mentioning dis-
> satisfaction with the new method of enabling/disabling Firebug. I am
> yet another developer who loves Firebug and uses it daily as a vital
> development tool. I am also, however, disappointed with the new
> disable/enable method, which is simply whether or not Firebug is open
> or closed. For me it's not *nearly* as easy to use because when I
> switch to another tab and I had drilled down to a location in the HTML
> to inspect an item in the previous tab, I lose that location.
I don't understand the connection between enabling/disabling and
location. This sounds like a bug to me, please give step by step
instructions in terms of the button labels in the UI to reproduce your
problem.
>
> There are other use cases for me also, for which this new schema does
You need to be specific. We can't guess based on "other".
> not work. I saw a note on the project page from developers suggesting
> that this new method will satisfy 80% of users, but I would venture to
> strongly suggest that a poll, even if an informal one, is in order to
> determine the correctness of that assumption. If it turns out that 80%
> of the users are frustrated and only 20% like this new system, that
> might shed new light on how best to proceed.
What page are you referring to? In any case, we are not interested in
solutions that fail for 20% of the users, you must be misinterpreting
our message.
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
-~----------~----~----~----~------~----~------~--~---
