On Jul 1, 3:38 pm, sir_brizz <bj.car...@gmail.com> wrote:
...,
> one step. Second, in 1.4 depending on the state of the current page,
> it would be:
> Click the bug
> Refresh the page
The page reload is only needed if you have never activated the page
before.
>
> Still, the margin of error in 1.4 is significantly higher when all is
> said and done due to the functionality of "closing" the panel (as
> opposed to minimizing it). In 1.3 this is of no concern, since, once
> you enable Firebug for a domain, you have to very specifically disable
> it for that domain in order for it to stop functioning. In 1.4 I only
Hmm, so now you are saying that because its hard to deactivate Firebug
in 1.3 its a good thing?
> have to unintentionally click the x button and complete deactivation
> takes place.
We added a minimize button. I'm sorry you'll just have to learn to use
it. It just a few pixels to the left.
>
> I've been using 1.4 off and on for the last several months, and I've
> not gained any ounce of respect for this activation model. I think
> it's rather telling that all along its development the question was
> asked "how should [some process] function?", a question which simply
> did not apply to the old model at all. For example, if I enable
In this regard I can speak from experience in the development of 1.3.
There more questions and quite a lot complains.
> Firebug on a tab and minimize it then browse to another page, it is
> disabled on the following page. Presumably, it only enabled for the
> first page and not for the current tab, yet if I have the panel up it
> stays active for the tab on every page. How should this function? In
> 1.3 there was no question. If the panel wasn't enabled for the
> following page's domain, you would just enable it and refresh and you
> were done taking action. In the new model, you have to wonder about
> what Firebug should be doing in this scenario, which immediately makes
> the model more complicated than it should be. I would think that the
> tab rule should apply here, since Firebug was enabled inside the tab.
> But, of course, that's not how it works.
I'm sorry but I can't sort out what you are saying here. I suggest
that if you can give the individual steps by the buttons then your
reaction or issue it will be easier to understand.
>
>
>
> > > So, how can we continue to claim this is not more complex? It
> > > absolutely is!
>
> > Because 1 < 5. Give it a chance.
>
> But, really, you're saying that 1 or 2 is less than 1. (And that is
> not considering the number of steps on ensuing pages in a domain,
> although this appears to have been fixed in the latest alpha of 1.5)
Yes, based on discussions in this group including ones you contributed
to I realized there was a simple and coherent way to support same-
domain activation. Try it and let us know.
jjb
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Firebug" group.
To post to this group, send email to firebug@googlegroups.com
To unsubscribe from this group, send email to
firebug+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---
