What steps will reproduce the problem? 1. Open the command line, try to run something. -> no auto-completion, and nothing gets run.
The command editor is unaffected. The problem seems to be that XBL initialization order changed, somehow, so that Firebug.chrome.$() is no longer usable from within CommandLine.initialize.
Comment #1
Posted on Jul 16, 2014 by Grumpy CamelHonza, how do you feel about this commit? https://github.com/simonlindholm/firebug/commit/3d6f37a78d747ab3ee1bb5055ac1962454902623
Comment #2
Posted on Jul 21, 2014 by Massive WombatSorry for the delay!
I tried the patch, but it doesn't see to help... (applied on Firebug 2 master + Nightly)
Could I be doing something wrong?
Honza
Comment #3
Posted on Jul 21, 2014 by Massive WombatAh, found one problem on my side!
The problem now is that I can't see the original problem, the Command line just work for me ;-)
Honza
Comment #4
Posted on Jul 29, 2014 by Grumpy CamelDidn't manage to track down why it worked in a new profile, but pushing anyway because it seems like a reasonable fix in any case: https://github.com/firebug/firebug/commit/ac987688e577efe83aa5120d7db589da746cca13
Comment #5
Posted on Aug 14, 2014 by Massive WombatThis issue has been fixed in Firebug 2.0.3 https://addons.mozilla.org/en-US/firefox/addon/firebug/
(the XPI doesn't appear on getfirebug.com yet due to: https://bugzilla.mozilla.org/show_bug.cgi?id=1053646)
Please let us know how it works for you.
Thanks for the help! Honza
Status: Fixed
Labels:
Type-Defect
FF-33
console
Test-case-available
OpSys-Linux
fixed-2.0.3