Sure would like to get a test case so we can fix this. jjb
On Jan 13, 3:11 am, Wolfram Kriesing <[email protected]> wrote: > A workaround, when the error occurs, just do > 1) ALT+TAB away from firefox and > 2) and then back into FF > and it works for me > > Wolfram > > On 9 Jan., 05:18, webbower <[email protected]> wrote: > > > Ok... Firebug 1.3.0 is just getting weird for me. The Console is > > acting as if possessed and I'm getting a bunch of other bizarre error > > messages and file references for my AJAX pointing to Firebug's HTTP > > sniffer component rather than the AJAX call function I used. I'm > > downgrading. > > > 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 -~----------~----~----~----~------~----~------~--~---
