Archive for the 'Firebug Releases' Category

The Firebug team released Firebug 2.0.18. This is a maintenance release ensuring compatibility with latest Firefox releases.

The beta channel on AMO is also updated.

Firebug 2.0.18 is compatible with Firefox 30 – 52

Firebug 2.0.18 fixes issue 8030. The extension is marked as multi-process (e10s) compatible so, it isn’t blacklisted and users can continue installing it. This way Firebug can help users to easily migrate into built-in Firefox developer tools – in case it’s running in multi-process enabled browser. When opened in a multi-process Firefox, Firebug’s tools cannot be used. Firebug will then only assist the user with migration to Firefox’s built-in tools.

Storage Inspector – The Storage Inspector enables you to inspect various types of storage that a web page can use (cache, cookies, local & session storage, indexedDB).

Responsive Design Mode – Responsive Design Mode makes it easy to see how your website or web app will look on different screen sizes.

Animation Inspector – The Animation Inspector displays animations in the page synchronized along a timeline, with a draggable widget you can use to move to any point in the timeline and see the page at that point.

What about Firebug 2

Firebug 2 doesn’t work in multi-process browsers (i.e. e10s) and converting it is too complex, so it will stop working when e10s is activated in Firefox. You will be able to disable e10s for a while to keep using Firebug 2, but this won’t last forever.

We blogged last year about our effort to unify Firefox Developer tools and Firebug and we’ve made good progress since then. Now it’s time for the next step…

We’ve been working hard on refactoring existing Firebug 2 features and extensions so, they work together with new Firefox built-in developer tools and support recent platform changes like the new multi-process architecture (a.k.a ‘e10s’).

Many Firebug features have already been added to the built-in tools, and several Firebug extensions have been ported to be Firefox addons:

We’ve been also working on a follow-up Firebug 3 (a.k.a Firebug.next) extension that allows us to test features before we land them in Firefox. Firebug 3 contains further popular Firebug features like XHR Console Inspector (aka XHR Spy) and a DOM panel for Document-object-model inspection.

The best part of this extension is a new Firebug theme (in addition to existing Light and Dark themes) so, Firebug users can feel like home when switching into Firefox built-in tools.

Note that the XPI is not signed and so, you need to flip xpinstall.signatures.required to false to allow installation.

Here is a screenshot showing Firebug theme in action:

(yes, this is built-in devtools toolbox, not Firebug!)

The work on the theme has helped us support existing Firebug users, and also make sure that theme APIs are extensible enough and ready for developers who want to build themes.

Firebug 2 doesn’t work in multi-process browsers (i.e. e10s) and converting it is too complex, it will stop working when e10s is activated in Firefox.

We want to be ready when Firebug 2 stops working and we have come up with the following plan.

Integrate all Firebug 3 features into Firefox built-in tools and forward all Firebug users to it.

Replace Firebug 2 by releasing Firebug 3 (on AMO) only if we have to deliver any critical features missing in Firefox developer tools in an extension.

We are currently working on porting XHR Inspector (bug 1211525), DOM panel (bug 1201475) and Firebug theme (bug 1244054).

Don’t worry if you want to run multi-process browser (DevEdition or Nightly) now. We have introduced transition path that will allow you to move from Firebug 2 to built-in DevTools. See the following screenshot (Firebug 2.0.14).

This notification message appears if you are running Firebug 2.0.14 in multi-process Firefox. It allows to open built-in Developer Tools or choose to disable e10s and keep Firebug.

The Firebug team released Firebug 2.0.13. This is a maintenance release ensuring compatibility with latest Firefox releases.

The beta channel on AMO is not updated due to a new signing process (support for beta channels is currently in open beta phase). It’s recommended to use standard release channel on AMO (if you don’t know what AMO beta channel is, you are most likely using the right release channel).

The Firebug team released Firebug 2.0.12. This is a maintenance release ensuring compatibility with latest Firefox releases.

The beta channel on AMO is not updated due to a new signing process (support for beta channels is currently in open beta phase). It’s recommended to use standard release channel on AMO (if you don’t know what AMO beta channel is, you are most likely using the right release channel).

The Firebug team released Firebug 2.0.11. This is a maintenance release ensuring compatibility with latest Firefox.

The beta channel on AMO is not updated due to a new signing process (support for beta channels is currently in open beta phase). It’s recommended to use standard release channel on AMO (if you don’t know what AMO beta channel is, you are most likely using the right release channel).