On 2010-10-30 13:56, Steven Roussey wrote:
On Oct 29, 11:26 pm, Nicolas Hatier<[email protected]> wrote:
I don't think this has a link with the issue I'm reporting in this
thread. Mine is likely a memory/object corruption over time in Firefox
(or in Firebug, but I would guess Firefox). Yours is an activation
issue, Firebug should either close (or stay open and activate as the URL
didn't really change), but not stay in linger between the two states.
Nicolas
The example page I posted has the problem are removing absolutely
everything from the page, including the things that we inject into it.
In a sense, it is activated on stuff that is no longer there. We might
consider that our injection of stuff not being permanent.
Your issue may be something else, but such things are a time sinkhole
without a test case. I would focus on the areas that are difficult for
firebug to handle -- frames, iframes, and document.open type stuff,
and the timing of various operations (it could be a race condition). I
know that creating a repeatable test case is 90% of the work though...
I agree 100% with you. I'm not asking for a fix yet, I'm just trying to
find clues and advices to create such a test case. I thought Firebug
Tracing would be enough, but unfortunately it is no help here, so I'm
back to case 1.
Nicolas
-steve--
--
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.
