On Oct 29, 11:26 pm, Nicolas Hatier <[email protected]> wrote: > Steven, I see the same as you. However, this is not the same issue. > > When you click the Write Document button and the document.open() > happens, the URL doesn't change, but it appears to change in Firebug's > realm. Firebug is not set to be activated in the new page, but the thing > that usually closes Firebug when you navigate to an unmonitored page > doesn't seem to trigger. Firebug remains open, but doesn't activate, so > any action remains without effect. > > If, when in the "Hello, world" page, you reload the page with F5 or the > button, you will see Firebug close. You can then open it properly, > refresh the page again, and use it. > > 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... -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.
