On Aug 28, 11:42 pm, Perlover <[EMAIL PROTECTED]> wrote:
> > > 1) I have a big AJAX document, there many nodes of DOM (big table),
> > > nodes are made by script in document. I cannot present this document
> > > here
>
> > Of course this means we cannot be of much help.
>
> May be you cannot but i think may be anybody here can
Ok, by "we" I meant Firebug developers.
>
> > > 2) I have Firebug 1.2.0 (i don't know the beta number, but i see 1.2.0
> > > version in my Addon's list) and Firefox 3.0.1
>
> > If the Firebug icon in the status bar is orange, then the debug
> > listeners are on. As far as I know this test is 100% reliable. Orange
>
> I didn't write that i used debug functions of Firebug. I wrote about
> DOM structure (HTML DOM)
> ...
> gray
>
> > > think, the Firebug continues a tracing of DOM and when my script
> > > builds a DOM of new document again the Firebug traces this document.
> > > As well if i do menu "Suspend Firebug" between 3 & 4 points here then
> > > this doesn't help - i see 100% CPU eating during 30-40 seconds too. So
> > > i think Firebug continues a tracing of DOM even if i did "Suspend
> > > Firebug"
>
> > This suggests to me that your problem has nothing to do with Firebug,
> > or at least on with any effect we have seen before. If you Suspend
> > Firebug and the status bar icon is then Gray, none of that tracing
> > thing you imagine is in fact going on. Gray is Off.
>
> Really ?
Yes, really.
> But HTML DOM inspect functions ?
These functions -- in principle -- require no cost unless you are
using the panels.
> I wrote that problem occurs if i reload the page. If Firebug is
> disabled when gray icon that how does Firebug inspect DOM ? And does
> who show to me html DOM structure in Firebug's HTML panel ? It's a
> tracing functions of Firebug.
No tracing it used for these panels. At the time you use the panel the
view is build by query operations.
>
> > > My conclusion: If i run once a Firebug for Tab window and after i
> > > click Firebug icon again for hiding Firebug again then Firebug doesn't
> > > turn off a tracing of DOM even if i reload page. As i read in
>
> > That conclusion would be correct, but it is not what you said above.
> > You said that you Suspend Firebug then see CPU: if so I doubt your
> > problem is Firebug.
>
> I think that this Firebug bug. I tested it several times
> I can get orange icon if i do enabling Console/Script/Net/ options
> before. But i didn't this and could inspect DOM. In this case i saw a
> trouble after reloading a page (my first post)
But until you produce a test case there is nothing we can do.
>
>
>
> > > changelog there firebug should be disabled if i don't have a opened
> > > sub-window of firebug
>
> > I don't know where you read this so I can't help your re-interpret
> > this message. I do think this is a reasonable concept, but it was not
> > the original model of Firebug and any changes to the Firebug model
> > make users unhappy as we know.
>
> http://code.google.com/p/fbug/source/browse/branches/firebug1.2/docs/...
>
> ---
> * Instant on: when the Firebug UI is active, HTML, CSS, DOM views
> activate (minimal overhead)
Based on all the information I have, this is true: these views are not
updated unless you have the UI active.
You can change the information I have by providing a test case that
demos your problem.
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
-~----------~----~----~----~------~----~------~--~---
