Good job with the latest release

[LooieENG]

<borat>NOT</borat>

It sucks, why did you have to mess with the older version that worked
fine? Been getting ideas from Mozilla,eh?

[johnjbarton]

If you have a specific problem, please let us know.
jjb

[LooieENG]

Thanks for the reply. The problem is I upgraded to 1.4.

I found a solution though.

[Trevan Richins]

Wow! Amazing how people act.

[ShadowC]

Seriously, the FB 1.4 is performing really bad, particularly on the
DOM tab... I'm really thinking on uninstalling it until you guys have
a fix... I'd love to get more information about this... I've become
really accustomed to using this great tool and now my entire work
performance is a stake because of this, so I can understand other
people's hostile reactions.

I'd love more info on what the problem is with FB 1.4!

On Jul 24, 10:54 pm, Trevan Richins <TRich...@omniture.com> wrote:
> Wow!  Amazing how people act.
>

[SportsWar]

I also have a big problem with FireBug 1.4. It won't stay ON when the
browser is closed and re-opened. So, when it's time to use FireBug to
see what's going on with a particular ad (or blank ad), it's useless
because the plug-in has to be physically turned on, and by then it's
too late to get the information you need.

How can I revert to a past, and working, version of FireBug? 1.4 is a
huge disappointment.

Thank you,

Mike

[johnjbarton]

On Jul 24, 11:49 pm, ShadowC <shadowc...@gmail.com> wrote:
> Seriously, the FB 1.4 is performing really bad, particularly on the
> DOM tab... I'm really thinking on uninstalling it until you guys have
> a fix... I'd love to get more information about this... I've become

There is one report of a DOM performance problem:
http://code.google.com/p/fbug/issues/detail?id=1984

Note that the reported problem is on Firebug 1.3. So if you have new
problems on 1.4 its probably not caused by Firebug alone.

> really accustomed to using this great tool and now my entire work
> performance is a stake because of this, so I can understand other
> people's hostile reactions.

I don't follow the logic here. Your success depends upon Firebug so
you understand why people want to discourage work on it?

> I'd love more info on what the problem is with FB 1.4!

Me too! So how about giving a detailed account of your problem so we
can fix it?

jjb

[johnjbarton]

On Jul 25, 6:40 am, SportsWar <inga...@sportswar.com> wrote:
> I also have a big problem with FireBug 1.4.  It won't stay ON when the
> browser is closed and re-opened.  So, when it's time to use FireBug to
> see what's going on with a particular ad (or blank ad), it's useless
> because the plug-in has to be physically turned on, and by then it's
> too late to get the information you need.

Yep, sure sounds like a big problem. Other people have reported
similar issues, but no one has come up with a test case for this
problem.

In all previous cases that I know about, installing Firebug in a new
Firefox profile fixes the problem.

If you can give a detailed description (what the buttons you push step
by step and the results) we might learn something about the problem.

If you run the tracing version with ACTIVATION on and post the trace
we will learn a lot.

>
> How can I revert to a past, and working, version of FireBug?  1.4 is a
> huge disappointment.

All versions of Firebug are available on http://getfirebug.com/releases.

jjb

[SportsWar]

Thanks for the reply. The older versions of FireBug would run in the
background, all of the time. I specifically use the Net tab with ALL
so that I can see what's loading on my web page. The purpose of
FireBug, at least for me in this particular industry, is to see what
ad server is being called when ads are loading onto the page. FireBug
has been a HUGE help with regard to locating problem ads (or even
blank ads) from third party ad networks. The information provides
proof of exactly what was called and allows the ad networks to locate
the problem quickly.

FB 1.4 does not run in the background, or at least I don't know how to
make it stay ON all of the time. As soon as I close my browser, even
if FB is just minimized, once I turn it back on the little bug in the
status bar comes up gray. If I don't remember to physically turn it
back on and I get a problem ad, it's already too late to do anything
about it because the 'Net panel was not active'.

I'll try going to the link you provided and just install the older
version as that was working perfectly. Hopefully you can find a way
to set up the new version so that it will act like the older ones.
Until now, I've been very pleased with the software.

Mike

[johnjbarton]

On Jul 25, 12:03 pm, SportsWar <inga...@sportswar.com> wrote:
> Thanks for the reply. The older versions of FireBug would run in the
> background, all of the time.  I specifically use the Net tab with ALL
> so that I can see what's loading on my web page.  The purpose of
> FireBug, at least for me in this particular industry, is to see what
> ad server is being called when ads are loading onto the page.  FireBug
> has been a HUGE help with regard to locating problem ads (or even
> blank ads) from third party ad networks.  The information provides
> proof of exactly what was called and allows the ad networks to locate
> the problem quickly.
>
> FB 1.4 does not run in the background, or at least I don't know how to
> make it stay ON all of the time.  As soon as I close my browser, even
> if FB is just minimized, once I turn it back on the little bug in the
> status bar comes up gray.  If I don't remember to physically turn it
> back on and I get a problem ad, it's already too late to do anything
> about it because the 'Net panel was not active'.

Firebug status bar icon right click "On for all pages".

>
> I'll try going to the link you provided and just install the older
> version as that was working perfectly.  Hopefully you can find a way
> to set up the new version so that it will act like the older ones.
> Until now, I've been very pleased with the software.

Just so you know we have no such plans. If you have a specific
request, you need to let us know.
jjb

[ShadowC]

I think the problems with Firebug 1.4 are still quite big for me to go
into deep analysis of them. The problem with the DOM inspector is
quite new for me, it is only happening since I got Firebug 1.4 on FF
3.5 (3.5.1) and no Firebug update has fixed it for me yet.

The problem you link to seems to be quite related, but as of right
now, inspecting ANY DOM object on ANY page renders Firefox completely
unusable for long seconds (some times even up to 25/30 seconds) and
this happens every time you try to interact with interface. So we
might be speaking here of an entirely new problem.

I have no other extensions that manipulate DOM, but if you want I can
take 5 minutes to set up a FF3.5.1+FB1.4 on a virtual machine with no
other interference just to prove that the problem is within Firebug.

I'm not discouraging the use of Firebug, I'm just encouraging you guys
to fix it, if you think you have enough reason and retribution for
doing it.

[johnjbarton]

On Jul 26, 11:22 am, ShadowC <shadowc...@gmail.com> wrote:
> I think the problems with Firebug 1.4 are still quite big for me to go
> into deep analysis of them. The problem with the DOM inspector is
> quite new for me, it is only happening since I got Firebug 1.4 on FF
> 3.5 (3.5.1) and no Firebug update has fixed it for me yet.

And my prediction is that no future Firebug update will fix it
either. Because I don't believe this is a Firebug problem. But you
don't have to agree with my belief, there is a simple test, see about
a new profile in http://groups.google.com/group/firebug/web/faq-about-firebug.

>
> The problem you link to seems to be quite related, but as of right
> now, inspecting ANY DOM object on ANY page renders Firefox completely
> unusable for long seconds (some times even up to 25/30 seconds) and
> this happens every time you try to interact with interface. So we
> might be speaking here of an entirely new problem.

I don't have this problem. No one else reports it.

>
> I have no other extensions that manipulate DOM, but if you want I can
> take 5 minutes to set up a FF3.5.1+FB1.4 on a virtual machine with no
> other interference just to prove that the problem is within Firebug.

What I suggest is that you install Firebug 1.4 in a new Firefox
profile. I predict that will prove that the problem is *not* within

Firebug.

>
> I'm not discouraging the use of Firebug, I'm just encouraging you guys
> to fix it, if you think you have enough reason and retribution for
> doing it.
>

And I am encouraging to try my suggestion, if you want Firebug to work
for you.

jjb