I've set that to false. But, the command editor has been working fine this morning. I'll have to keep an eye on it and see. Perhaps I should set extensions.firebug.enableOrion back to true until the problem reappears, and then try setting it to false?These sporadic issues are rough to pinpoint. Thanks for the help, though. Scott
On Wednesday, November 7, 2012 4:38:47 AM UTC-7, Jan Honza Odvarko wrote: > > If you set extensions.firebug.enableOrion to false (so, no syntax > coloring) > Can you use the Command Editor then? > > Honza > > On Nov 6, 7:46 pm, Scott Taylor <[email protected]> wrote: > > I'm using Firefox 16.0.2, Firebug 1.10.6 and I am on Windows 7. Sorry > > should of put that in the first time. > > > > The only Javascript warning I get is > > > > Timestamp: 11/6/2012 11:42:03 AM > > Warning: Use of Mutation Events is deprecated. Use MutationObserver > instead. > > Source File: chrome://browser/content/orion.js > > Line: 3408 > > > > but I'm not seeing any errors. > > > > Scott > > > > > > > > > > > > > > > > On Tuesday, November 6, 2012 10:00:25 AM UTC-7, Scott Taylor wrote: > > > > > Can anyone tell my why my command window might be greyed out and > unusable? > > > When I reduce it to a command line, it is fine. This is a frequent > problem, > > > but doesn't always occur. Sometimes a FF restart fixes, but just as > often > > > it doesn't. We use Firebug a lot in a class I am taking, so this is > > > becoming very frustrating. I tried to post a screen capture of it, but > > > Google doesn't seem to like that. Any ideas about this would be > awesome. > > > > > Scott > -- 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 https://groups.google.com/forum/#!forum/firebug
