Firebug Releases: 1.3.1 … er 1.3.2
robcee sent Firebug 1.3.2 off to addons.mozilla.org yesterday. This version includes fixes for the Firebug’s activation, several fixes for the command line, as well as file locking and net panel fixes. Honza has been working with the babelzilla Firebug team to improve the localizations as well. (We are up to 22 locales by now).
At the end of 1.3.1 we discovered that the new Script panel does not work on Firefox 2 because we don’t get a scroll event we expected. Since Firefox 2 isn’t being maintained and since many improvements in Firebug 1.3 depend upon Firefox 3, we decided to change the minVersion requirement in Firebug 1.3 to Firefox 3.0. That’s the only change between Firebug 1.3.1 and Firebug 1.3.2.
jjb
February 6th, 2009 at 11:09 am
Not sure if this is the appropriate place; however, with version 1.3.2 in FF 3.0.6, the status bar image for Firebug is always gray, no matter if it is suspended or not. Not sure if this is intended behavior or not. Previously it would have some coloration to it while active.
Regards,
Mark H.
February 6th, 2009 at 11:18 am
the best place to file a bug is on http://code.google.com/p/fbug/issues. You can get there directly from the “bug menu” icon on the left of the Firebug panel itself.
And no, that’s not the intended behavior. The bug should be orange when Firebug’s active and grey when suspended or not active. You might want to try opening a blank tab (about:blank) and deactivating System Pages in console, script and net panels. Suspend on the status icon’s context menu should also work, but I’m guessing you’re having trouble with that.
February 6th, 2009 at 2:53 pm
OK, if I activate any of the 3 panels then the bug becomes colorized. If I then use the context menu to suspend then it will grey and colorize when I resume. If I deactivate all 3 panels then it greys out no matter the status of the context menu. Before it would remain colorized until I actually suspended it via the context menu, even if all the panels were deactivated. So, I’m not sure which visual cue is technically correct/bugged. Anyway, will use the other spot if any further discussion is needed.
Great plug-in btw. It’s helped me to get some of my pages displaying correctly to know what CSS aspects to change.
Regards,
Mark H.
February 8th, 2009 at 3:05 am
[...] Lipskas on February 8, 2009One of the best debugging tools for web developers has received an update. This version includes fixes for the Firebug’s activation, several fixes for the command line, as [...]
February 8th, 2009 at 6:25 am
apparently the new version conflicts with Foxmarks add-on: http://code.google.com/p/fbug/issues/detail?id=1460
February 8th, 2009 at 7:33 am
[...] Auffallend ist, dass nach der Version 1.3.0 direkt die Version 1.3.2 veröffentlicht wurde. Laut dem Firebug Entwickler-Blog wurde nach dem Release 1.3.1 leider festgestellt, dass das neue Script Panel in FF2 nicht korrekt funktionierte. Weitere Informationen unter http://blog.getfirebug.com/?p=82. [...]
February 12th, 2009 at 9:40 pm
If i tried to open JS file from script tab, i got this: Failed to load source for sourceFile top-level http://62.119.142.107:8888/pravattestcustomer/ubiqo/ubiqo.js script.tags( X| 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 )
Is that bug on FireBug or feature? or what error I am doing
February 16th, 2009 at 6:18 pm
pravat: Please try 1.3.3b3, this problem has been fixed.