On Jul 3, 10:55 am, johnjbarton <[email protected]> wrote:
> On Jul 2, 7:21 pm, sir_brizz <[email protected]> wrote:
> > 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.
Well, I guess that is part of my confusion about 1.4. It seems an
extraordinary amount of time was spent on something that is hugely
complex and doesn't even really contribute to the core functionality
of Firebug. That's why I would have thought a more simple and flexible
system would have been adopted moving on from 1.3.
> > 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.
I don't really want that. I'd rather just have "If Firebug is not
showing and you go to another page, continue not showing Firebug". It
doesn't make sense to have it popping up and minimizing all over the
place. Currently there is no way to BOTH minimize and close Firebug
for a page when "On for all pages" is checked, therefore if I want
firebug to stay minimized and turn it off for a page, I can't.
> > 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.
Okay, this makes sense. But it is confusing, I wouldn't expect "Off
for all pages" to change domain settings based on what "On for all
pages" does (unless... does "Off for all pages" only disable domain
settings while it is checked?? If so, that's probably fine...)
> > 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.
I wouldn't expect it to, really. I realize that it's possible to have
Firebug active and not showing, but based on the other functionality,
it doesn't seem like that would work.
>
> 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
-~----------~----~----~----~------~----~------~--~---
