I don't know if it even a bug yet, or if there is anything we can do about it. jjb
On Jul 14, 8:37 am, Mike Walters <[email protected]> wrote: > Has this been resolved, its a pretty annoying bug? I have to kill the FF tab > and open a new each time this occurs.~m > > On Fri, Jul 10, 2009 at 1:33 AM, johnjbarton > <[email protected]>wrote: > > > > > We would appreciate this info in a bug report to consider it further: > > >http://code.google.com/p/fbug/issues/list > > > jjb > > > On Jul 9, 8:34 am, amartinez <[email protected]> wrote: > > > Not sure if this is just a FF3.5 / Firebug 1.4x.0b7 issue, but the > > > following line of code can cause Firebug to stop working. I do not > > > know enough about extension development to make a call on whether this > > > is an issue or not, but I figured it might help some poor soul out. > > > > if(false){ var console = {} } > > > > Even though the if statement fails, it will cause Firebug to throw the > > > following errors and cause the console to stop working when you > > > actually expand Firebug and click on the console's command line. > > > > > Firebug cannot find _firebugConsole element true Window <site address> > > > > redeclaration of var console > > > > This same script will not cause any issues if the key word 'var' is > > > removed (e.g. if(false){console = {} } ). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
