On Jul 2, 7:21 pm, sir_brizz <[email protected]> wrote:
> I'm just unsure what clarity was actually lost in the 1.3 model. If
> you had enabled Firebug for a domain, then it was on on that domain.
> You could have expanded this by introducing the bug lit/unlit design
> you have for 1.4 now to show whether Firebug was active on the page or
> not. Who cares what the panel is doing? If you want to know if Firebug
> is on, just look at the bug. ...
The Firebug icon is orange when the optional panels Console/Script/Net
are operating. This is the same in Firebug 1.3 and 1.4.
> As before, I realize the current model makes some sense, I just don't
> see it as a worthwhile change over what we had. As someone who heavily
> prefers the 1.2 design to this day, I would much prefer just being
> able to have firebug either always on or always off and then have
> domain settings for the opposite action to occur.
Now you are reminding me how much time I've wasted on this stuff.
>
> I realize all of this isn't going to go anywhere, the core development
> team is happy with the activation model regardless of what any
> individual person wants, so nothing is likely to change as far as how
> the model is functionally.
I would not say "happy", more like "allowing deactivation was a waste
of time". In retrospect I think we should never have implemented
activation at all. Rather we should have just made Firebug "on", end
of story. If it makes using Firefox for your gmail impossible, sorry,
we do debuggers not email clients. That would have made 1.2 hugely
unpopular and cut the number of users by a large fraction and possibly
prevent Mozilla from contributing to the project. On the other hand, I
would been able to concentrate on things that make more difference to
debugging.
>
> So roping this all back in to what can actually happen for the current
> design, the X is confusing in "On for all pages" mode. I understand
> that it isn't doing the blacklisting of the domain, though that might
> be a nice feature, but, in my opinion, the state of the panel itself
> (showing or hidden) should stay static across all pages when the
> option is set.
Yes we could have On For All Pages obey the black list settings. But
I'm not sure that would be less confusing.
>
> On another note, I don't really get the "Off for all pages" option. Is
> that for debugging? Or does it change your per-domain settings in some
> way? Because unchecking "On for all pages" should just revert to your
> original settings.
Unchecking "On for all pages" stops whitelisting new pages. It does
not change any existing annotations.
"Off for all pages" clears the whitelist. So yes in fact it is a
debugging feature.
>
> The thing I dislike most about 1.4 is that Activation is linked sooooo
> tightly to the panel displaying. It doesn't feel like these things are
> separate at all anymore, so it feels like it is "Panel showing,
> Firebug active. Panel not showing, Firebug inactive" (despite the fact
> that that is not quite how it works) and I hate that to extreme
> levels.
"Panel not showing, Firebug active" is minimize.
Panel showing, Firebug inactive is not supported, correct.
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
-~----------~----~----~----~------~----~------~--~---
