I'd recommend always using top.console. The console reference usually isn't installed on subframes.
ss On Fri, Dec 17, 2010 at 11:08 AM, Nicolas Hatier <[email protected]>wrote: > I know this isn't the answer you are looking for, but to test for console > you should use "window.console" rather than "console" alone, such as: > > if (!window.console) { > alert(1); > > } > > On 2010-12-17 04:46, Dominik Deobald wrote: > >> I have a problem with the current version of FireBug. >> >> Firefox: 3.6.13 >> Firebug: 1.6.0 and 1.6.1b1 (tried both) >> >> My Javascript can't use console.log (or any console at all) to output >> debug messages. I'm not sure when it stopped working, but for now I >> get an "console is not defined" when I try to access it or a message >> popup when I run this code: >> >> if (console == undefined) { >> alert(1); >> } >> >> I had the latest FirePHP extension (DeveloperCompanion) installed but >> removed it to see if that was causing the problem. Didn't change >> anything though. >> >> Any ideas? Is this happening to someone else, too? >> >> > -- > 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]<firebug%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/firebug?hl=en. > > -- 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.
