On 2010-10-29 14:13, John J Barton wrote:
Unfortunately, according to the trace, the console loaded properly.
So either the console in the sub-windows is being erased or it was not
loaded into the sub-window even if the trace says so.
Are you doing anything to the sub-windows 'window' object?
I'm doing many document.open("text/html", "replace") on them. The issue
does not appear immediately, only after a while and several refreshes.
No document.open() occur between the refresh and the appearance of the
error log lines.
Maybe the way you open the subwindows is related to this issue.
I think a test case will be needed....
As I said, this is not easily reproducible, it just happens after an
hour or so of work, without an apparent cause. Something gets corrupted
somewhere in Firebug or Firefox and prevents Firebug from loading itself
correctly in iFrames.
Nicolas
jjb
On Oct 29, 9:57 am, Nicolas Hatier<[email protected]> wrote:
On 2010-10-29 12:42, John J Barton wrote:
On Oct 28, 11:01 pm, Nicolas Hatier<[email protected]> wrote:
Ok, got some time to redo the test and tracing.
With COMMANDLINE enabled, I see no error in the tracing window (nothing
in red). Maybe the attached log could enlighten you.
While lines 12 to 19 are being sent to the tracing window, the error
console gives the same usual error:
uncaught exception: _FirebugCommandLine init failed in http://<session
url>/blank.wssp because TypeError: window.loadFirebugConsole is not a
function
uncaught exception: _FirebugCommandLine init failed in http://<static
url>/blank.html because TypeError: window.loadFirebugConsole is not a
function
uncaught exception: _FirebugCommandLine init failed in http://<static
url>/blank.html because TypeError: window.loadFirebugConsole is not a
function
Thanks, it is clear from the call stacks that the subwindow command
loading is failing:
Firebug.CommandLine.injector.attachCommandLine(context,
context.window);
for (var i = 0; i< context.windows.length; i++)
Firebug.CommandLine.injector.attachCommandLine(context,
context.windows[i]);
Based on the error message, the console attach did not succeed. The
command line (dev input) gets it output by using the console.log().
Please trace the same test case with CONSOLE set. That will tell us
about the progress of attaching the console.
Tracing log with CONSOLE and COMMANDLINE set
NH
jjb
firebug-tracing-logs.ftl
424KViewDownload
--
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.
