Some back story is needed in order to explain why the extension is now set up in this manner. When you now click Firebug for a site you’ll encounter an interface that looks something like this: It’s also a, seemingly, bizarre addition to the extension. This is the most drastic UI change of the release. We’ll be discussing the specific nature of these changes once everyone has had enough time to upgrade to Firebug 1.2.Ī list of all the bug fixes can be found in the full release notes. Specifically the Console panel has seen a number of security improvements. They’re all much more performant and have a huge number of bug fixes. The Script panel (the JavaScript debugger), the Net panel (network monitoring), and Console panel have all seen considerable updates. The most common report of Firebug problems has been related to running Firebug 1.1 in Firefox 3 – which is a mess (hence Firebug 1.2). If it’s anything other than 1.2.0bX (where X is a number 1-15) you’ll need to forcefully go to the above Firebug URLs and install the new version (the auto-update isn’t working for older versions). Go to Tools > Add-ons in Firefox and see what version of Firebug you’re running. Now is a good time to verify the version of Firebug that you’re using. If you’ve been using the Firebug 1.2 betas you’re already on top of this. Some of the major points of this release include:

There have been a number of improvements made (not to mention countless bug fixes). John J Barton and Jan Odvarko put a ton of work into this release (you may have noticed the rapid-fire series of beta releases last week – just trying to smooth out the rough edges). The release should be up on the Mozilla Add-ons site today, but it’s also up on right now.

The final version of Firebug 1.2 has been released.

Firebug download for firefox 27