On Oct 24, 1:33 pm, Nicolas Hatier <[email protected]> wrote:
> Hello.
>
> Since many, many releases of Firebug, I often get, after working for a
> while, this:
>
> uncaught exception: _FirebugCommandLine init failed in <iframe_1_url>
> because TypeError: window.loadFirebugConsole is not a function
> uncaught exception: _FirebugCommandLine init failed in <iframe_2_url>
> because TypeError: window.loadFirebugConsole is not a function
> uncaught exception: _FirebugCommandLine init failed in <iframe_3_url>
> because TypeError: window.loadFirebugConsole is not a function
>
The command line initialization code did not find window.console, so
it's desperately trying to load the console....
> I have 2 hidden IFrame and one visible in my application, which all
> start with a blank.html src. When I start Firefox and begin to work, no
> problem. After a while, after a refresh, those begin to appear. I've not
> been able yet to find a fixed pattern or a test case for this issue, and
> it didn't really matter cause these were doing no harm.
>
> It it matters, blank.html contains exactly this: "<html><head><style
> type="text/css"> body { border:0} </style></head></html>"
...but the console injection did not run because their is no
Javascript in the page to trigger it.
>
> However, since a recent release (1.6 b2, I think), Firebug began to
> break on those errors. As there is no source for them, Firebug breaks at
> the beginning of an almost empty HTML file which is the initial URL for
> each IFrame.
>
> It means that, each time I refresh the page, I have to hit Continue
> three times for my application to start. And as there is no source for
> the errors, the breakpoint balloon does not appear at all, so I can't
> tell Firebug to ignore them. The only way to continue working normally
> is to restart Firefox.
>
> Could you help me help you fixing that bug?
Firebug > Firebug Icon Menu > Open Tracing > Options > ERRORS and
FBS_ERRORS. Find the error message and see if we have a call stack.
That will point to the code that is calling for command line
initialization.
But I guess at the problem: you are using the command line on the main
page. That cause a focus event on reload, triggering command line
init. Firebug iterates through the sub windows and inits the command
line. The sub windows without JS fail as above.
Do you get the error if you don't have the command line focused when
you reload?
jjb
>
> Regards
> Nicolas Hatier
--
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.
