Upgrade to Firebug 3 is definitely the recommended option. If you install Firebug 2 into a multiprocess (e10s) enabled browser, you’ll be prompted to upgrade to Firebug 3 or switch off the multiprocess support. Firebug Compatibilityįirebug 2.0 is compatible with Firefox 30 – 36 and will support upcoming non-multiprocess browsers (as well as the recently announced browser for developers).įirebug 3.0 alpha (aka Firebug.next) is currently compatible with Firefox 35 – 36 and will support upcoming multiprocess (as well as non-multiprocess) browsers. So Firebug, built on top of the existing developer tools infrastructure that already ensures basic interaction with the debugged page, allows us to focus more on new features and user experience. All these features require heavy interaction between a tool and the page content. Various CSS and DOM inspectors not only display internal content data, but also allow the user to edit them and see live changes. Tools usually collect a large amount of (meta) data about the debugged page and present it to the user. This often means that many of the existing synchronous APIs will turn into asynchronous APIs.ĭeveloper tools, including Firebug, deal with the content in many ways. message manager or remote debugging protocol). Every time an extension needs to access the web page it must use one of the available inter-process communication channels (e.g.

The add-on’s code will run in a different process (browser chrome process) from web page content (page content process) - see the diagram below. The main challenge (for many extensions) is solving communication problems between processes.

The e10s project introduces a great leap ahead in terms of security and performance, as well as putting more emphasis on the internal architecture of add-ons. The two major advantages of this model are security and performance. The goal of the Electrolysis project (“e10s” for short) is to run web content in a separate process from Firefox itself. This is important especially for upcoming multiprocess support in Firefox (also called Electrolysis or E10S). This direction allows simple use of available platform components. There are several reasons why having Firebug built on top of native developer tools in Firefox is an advantage - one of them is tight integration with the existing platform. This version represents the next generation of Firebug built on top of Firefox native developer tools.

Firebug 3 alpha was announced couple of weeks ago.

Firebug download for firefox 30