On 2010-10-31 20:23, Steven Roussey wrote:
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.
Not really. John said that it did attach correctly. So it is not that.
It might be something related to document.open stuff (perhaps no
matching close or something like that?). And perhaps you should send a
console.info() every second in a timer on your page, and you can see
just when it stops working.
It doesn't stop working as it works in the outermost page.
However when the bug appears it spurs unwanted warning each time I
refresh the page (I refresh the page a lot while testing), and since the
latest Firebug release it breaks on those warnings, forcing me to click
Continue three times for each refresh, or restart the browser until it
happens again.
N.
-s
--
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.
