Archive for March, 2011

Firebug Lite 1.3.2

Wednesday, March 23rd, 2011

Firebug Lite 1.3.2 is finally out and it comes with important fixes and enhancements!

Check the Firebug Lite page for installation details of the the cross-browser version. Or, if you are a Google Chrome user, check the Firebug Lite for Google Chrome page.

This release fixes 6 issues: 4 bugs and 2 enhancements. There’s also the addition of the cool infoTips module.

Bugs fixed:

  • Issue 3422: Firebug Lite breaks Google Instant Search
  • Issue 3504: Firebug lite: jQuery.ajax call fails in IE
  • Issue 3524: Firebug Lite Style Panel doesn’t work if the native Element is extended
  • Issue 3554: Firebug Lite should use local images when loaded locally


  • Issue 3166: Listen to F12 key in for Google Chrome when inactive
  • Issue 3579: Use context menu to Inspect Element in Firebug Lite Chrome Extension


  • infoTips for CSS properties such as colorand image

A bug in the XHR watcher was affecting XHR calls in IE (Issue 3504) and in some applications like Google Instant Search (Issue 3422). The XHR Listener relies on replacing the XMLHttpRequest object with a proxy one in order to be able to track XHR calls. This is an intrusive approach and can potentially affect other applications. On the other hand, there is no other automatic way to track XHR calls using only JavaScript, and the benefits of having such feature in Firebug Lite are considerable (able to see GET and POST variables, response headers, view data as JSON, HTML or XML). Now all known problems are fixed but to avoid future problems with Firebug Lite affecting other applications a new option “Disable XHR Listener” was created. You can set this option using the Firebug menu, or using the other options described here.

New "Disable XHR Listener" option

Another important fix is Issue 3524 which was making the Style/CSS Panels to fail in sites like Joomla (or any other site that extends the native Element object for that matter). So enjoy, now you can tweak the CSS of Joomla sites! Also, regarding the Style/CSS panels, the infoTips module has been ported from Firebug so now you can see that little popup showing colors and images of the CSS file.

The hard work is actually happening behind the scenes, refactoring Firebug Lite’s core in order to support sharing modules with Firebug. The Chrome extension code was also refactored and the communication between the “isolated worlds” (Firebug Lite / Content Script / Background Page) was improved, which allowed the context-menu integration to be implemented (Issue 3579). Now if you right click on Chrome you’ll se a “Inspect with Firebug Lite” option. Thanks to Jake Goldsborough for motivating me working on this. I also refactored the Chrome extension’s activation. Now it is possible to activate Firebug Lite extension using the F12/ctrl+F12 key (Issue 3166).

Context-menu integration in Google Chrome

I wish I had released this version a long time ago but a lot of stuff is going on and I had some problems along the way. I just want to express my sincere apologies for the long period without updates.

Please post feedback in the newsgroup.

Pedro Simonetti.

Firebug 1.7.0

Monday, March 21st, 2011

After eleven alphas and four betas Firebug Working Group (FWG) is proud to declare victory and release the final Firebug 1.7.0! Of course also Chromebug 1.7.0 is available.

This version fixes three bugs reported since the last beta.

The main goal of Firebug 1.7 has been full compatibility with Firefox 4 (released tomorrow!). However there are also new features and improvements. They have been all published here on this blog, so see just some highlights.

  • Break notification message redesign
  • Only show applied styles
  • Open with editor feature improved
  • Support for local, session and global storage examination in the DOM and Console panels
  • New API for Firebug extensions
  • New Firebug start button
  • Large command line has history
  • CSS panel is now displaying @font-face rules.
  • Pressing F1 opens a help page (Firebug UI must be opened and focused)
  • Inspector improved and solid as a rock!
  • Our automated testing framework improved and 150+ tests watching Firebug features

See more

The version has been also uploaded to AMO, but it can take some time to appear.

Last beta 4 is exactly the same as the final release so, beta testers subscribing to AMO beta channel will get all fixes included in final release (they won’t be updated to the final release automatically, that’s how AMO works).

Finally, take a look who is involved in Firebug development!

Please post feedback in the newsgroup, thanks.


Firebug 1.7b3

Thursday, March 17th, 2011 has Firebug 1.7b3 + Chromebug 1.7b3.

We have got couple of bug reports since yesterday and as we managed to quickly fix them we also decided to yet release b3 for our awesome beta testers!

  • CSS Properties in the Style side-panel can be disabled/enabled again (issue 4227)
  • JavaScript object are properly logged in the Console (issue 4209)

The minimum required Firefox version is 4.0 since this beta. We’ll cover even 3.6 as soon as we get some more feedback about stability.

Please post feedback in the newsgroup, thanks.


Firebug 1.7b2

Wednesday, March 16th, 2011 has Firebug 1.7b2 + Chromebug 1.7b2!

We have fixed 10 issues in this release. The most noticeable change is probably break notification UI (issue 4144). Not only the message doesn’t take so much space and so, more actual source code is visible, but it also nicely teaches the user about how to get it back if it’s been disabled.

Note the panel’s tab menu link that opens an important piece of UI.

I’d like to see this user experience more thorough Firebug UI since this approach solves well known problem puzzling a lot of users: Where I can enable it later, if I pick a “Do not display again button”.

See other issues for more details about what is improved in this version.

Final Firebug 1.7 release next week!

Please post feedback in the newsgroup, thanks.


Firebug 1.7b1

Friday, March 4th, 2011 has Firebug 1.7b1 + Chromebug 1.7b1!

Since Firefox 4 moves into its RC phase these days, Firebug also runs full steam ahead to be ready for final 4. We switched to beta since Firebug is in good shape and running well with Firefox 4 beta.

We hope to get more testers and feedback to be sure all is working as expected. Note that we are also maintaining a channel with Firebug beta releases on AMO. Download it and become a beta tester today! (you’ll be automatically updated when new beta is released).

All our tests pass and there is 26 issues fixed since the last alpha.

Here is a summary of highlights (new since the last alpha):

  • Only show applied styles in Style side panel (issue 223). If you dealing with a page that uses a lot of CSS rules and the Style side panel looks messy showing also overwritten declarations, you can utilize a new Only Show Applied Styles filter.

  • Goto a line number available in the Script panel is now more visible in the UI (issue 887).1. Switch to the Script Panel
    2. Scroll the Script Panel
    3. Press Ctrl+L
    4. Check the search-box that indicates what to do…

  • Do you use “Open With Editor” feature? Now you can pass even a line number when invoking an editor. This way you can start script editing immediately at the right place and avoid tedious scrolling (issue 1480).
  • Better representation of the Date object within Firebug console (issue 4088). If you log a date object into the console you can see its actual value now.
  • Firebug console also supports logging of the globalStorage field. See following screenshot with an example.

  • Extending Firebug: better API for reusing an info-tip within a Firebug extension (issue 4175).

Other new features introduced during the alpha phase are described in previous posts.

Please post feedback in the newsgroup, thanks.