blog
discuss
releases
documentation

Archive for the 'Firebug Releases' Category

Firebug 2.0.14

Monday, February 8th, 2016

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

 

Firebug 2.0.14 is compatible with Firefox 30 – 46

Firebug 2.0.14 fixes the following issues: 7954, 7964, 7961, 7956.

 

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 read more

 

Please post feedback in the newsgroup, thanks.

Jan ‘Honza’ Odvarko

 

Merging Firebug into the built-in Firefox Developer Tools

Monday, February 8th, 2016

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.

Beta version of Firebug.next is available for download.

 

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:

DOM panel
(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).

Firebug running in multi-process browser message

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.

Happy debugging!

 

Jan Honza Odvarko (Firebug Working Group)
and
Joe Walker (Firefox Developer Tools)

 

 

Firebug 2.0.13

Monday, October 26th, 2015

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).

 

Firebug 2.0.13 is compatible with Firefox 30 – 42

Firebug 2.0.13 fixes the following issues: 7948, 7951, 7952, 7929.

 

Please post feedback in the newsgroup, thanks.

Jan ‘Honza’ Odvarko

 

Firebug 2.0.12

Wednesday, September 2nd, 2015

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).

 

Firebug 2.0.12 is compatible with Firefox 30 – 42

Firebug 2.0.12 fixes the following issues: 7916, 7922, 7928, 7917, 7923, 7931, 7918.

 

Please post feedback in the newsgroup, thanks.

Jan ‘Honza’ Odvarko

 

Firebug 2.0.11

Tuesday, June 16th, 2015

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).

 

Firebug 2.0.11 is compatible with Firefox 30 – 41

Firebug 2.0.11 fixes the monitor() and unmonitor() commands (issue 7907) as well as source code pretty printing (issue 7906).

 

Please post feedback in the newsgroup, thanks.

Jan ‘Honza’ Odvarko

 

Firebug 2.0.10

Monday, June 1st, 2015

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

 

Firebug 2.0.10b1 has also been released to update users on AMO beta channel. This version is exactly the same as 2.0.10.

 

Firebug 2.0.10 is compatible with Firefox 30 – 41

Firebug 2.0.10 fixes an issue with the Events panel (broken in Firefox 38) and small issue in the CSS panel.

 

Please post feedback in the newsgroup, thanks.

Jan ‘Honza’ Odvarko

 

Firebug 2.0.9

Thursday, April 9th, 2015

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

 

Firebug 2.0.9b1 has also been released to update users on AMO beta channel. This version is exactly the same as 2.0.9.

 

Firebug 2.0.9 is compatible with Firefox 30 – 39

Firebug 2.0.9 fixes 7 issues.

 

Please post feedback in the newsgroup, thanks.

Jan ‘Honza’ Odvarko

 

Firebug 2.0.8

Friday, February 6th, 2015

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

 

Firebug 2.0.8b1 has also been released to update users on AMO beta channel. This version is exactly the same as 2.0.8.

 

Firebug 2.0.8 is compatible with Firefox 30 – 38

Firebug 2.0.8 fixes 3 issues.

 

Note that Firebug 2.0.8 is not compatible with upcoming multiprocess (aka e10s) Firefox. You need Firebug 3 (aka Firebug.next) built on top of Firefox native tools to run with multiprocess browser. Firebug 3 is available as an alpha and you can download the latest version from our github repository. The team is currently fully focusing on Firebug 3.

 

Read more about why Firebug 3 is based on native Firefox tools and why some features are not yet ready in this thread.

 

Please post feedback in the newsgroup, thanks.

Jan ‘Honza’ Odvarko

 

Firebug 2.0.7

Tuesday, December 9th, 2014

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

 

Firebug 2.0.7b1 has also been released to update users on AMO beta channel. This version is exactly the same as 2.0.7.

 

Firebug 2.0.7 is compatible with Firefox 30 – 37

Firebug 2.0.7 fixes 1 issue.

 

Firebug 2.0.7 is not compatible with upcoming Multiprocess Firefox (read more about e10s), but we are already working on Firebug 3 (alpha available for testing) that is fully compatible. Note that Firebug 2 users will be automatically prompted for update when running in e10s enabled browser. The following panel will be displayed when clicked on Firebug start button. Read more about Firebug & e10s.

 

Please post feedback in the newsgroup, thanks.

Jan ‘Honza’ Odvarko

 

Firebug 3 – next generation of Firebug

Monday, November 10th, 2014

Summary: The world of web development tools is changing quickly and Firebug doesn’t want to stay behind. If you are Firebug fan or just curious what the future holds for Firebug and where the next Firebug generation is heading, read on…

 

 

In 2006, Firebug started a revolution of in-browser developer tools and it quickly became the most popular and powerful web development tool. Millions of people used Firebug to tweak their pages to perfection as well as understand and learn new web technologies. It was suddenly possible to inspect a web page from different angles and see how it’s created and how to improve it.

 

Firebug has inspired all main browser vendors to include similar tools in their products. Firebug itself has been developed as highly extensible application and it also inspired a lot of developers to create Firebug extensions.

 

Firebug has always been maintained as an independent open source project and it has received contributions from many people over time. Developers usually have many ideas about what would make them more effective in daily work and so, Firebug has naturally become a great tool made for developers by developers.

 

It has always been a handy tool. That’s one key of its success and that’s also why many users still prefer it even if there are other tools in the wild having more features. That said, Firebug helped web development to evolve by introducing a simple user interface.

 

Firebug 2

 

Firebug introduced new user experience designs as well as new web standards that have been widely adopted by other browsers and tools. For instance, Firebug stands behind the Console API standard, which represents the way to log debugging information. We introduced the HTTP Archive specification for page load performance analyses and also graphical web page breakpoints to make debugging easier and more effective.

 

Firebug is still a powerful web development tool used by millions of users around the world
who love especially its simplicity and great user experience, but it’s also facing new challenges. The biggest is the fact that it doesn’t make much sense for Firebug (as Firefox add-on) to duplicate functionality built into Firefox.

 

The product has always been an extension and the natural direction is to build the next Firebug generation on top of the existing developer tools in Firefox – and extend them. So, the next step is tight integration with the existing Firefox platform. This way Firebug also gets significant performance, stability and security advantages. Firebug will complement the Firefox Developer Tools by adding new functionality – not by competing with them.

 

The next Firebug generation starts with introducing a new Firebug theme, new features and bringing the great Firebug user experience to the built-in tools. Users don’t want two separate tools in Firefox – they want one great and powerful tool!

 

So, give it a try and install Firebug 3 alpha (you can also check out the firebug.next source repository). We’d love to hear feedback from you!

 

Update: Firebug 3 alpha is compatible with Firefox 35.0a2+

 

Firebug 3

 

Please post feedback in the newsgroup

Jan ‘Honza’ Odvarko