I'm seeing the same issue. To reproduce:
1) open console 2) declare "var foo = 2;". Note no response returned. 3) request foo by typing "foo" or calling "console.log(foo)". 4) note exception "message = foo is not defined", "error = ReferenceError" The new firebug also seems to interfere with other js code on my page when the console is enabled. Nate On Jan 7, 10:39 pm, webbower <[email protected]> wrote: > I just upgraded to 1.3.0 and in trying to write some custom > javascript, I seem to intermittently get the following error in my > console when I try to do console.log() or alert(): > > Firebug cannot find firebugCommandLineAttached attribute on firebug > console element, its too early for command line <div > id="_firebugConsole" style="display: none;" FirebugVersion="1.3.0"> > > It seems to start when I refresh my page, but then fixes when I switch > to another open tab in browser, run a JS command in that console, and > then switch back. > > Platform: Mac OS X 1.5.6 > Browser: Firefox 3.0.5 > > Thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
