On Jul 26, 11:22 am, ShadowC <[email protected]> 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
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
