Saying Goodbye to Firebug

The most popular and powerful web development tool.

Firebug has been a phenomenal success. Over its 12-year lifespan, the open source tool developed a near cult following among web developers. When it came out in 2005, Firebug was the first tool to let programmers inspect, edit, and debug code right in the Firefox browser. It also let you monitor CSS, HTML, and JavaScript live in any web page, which was a huge step forward.

Firebug caught people’s attention — and more than a million loyal fans still use it today.

So it’s sad that Firebug is now reaching end-of-life in the Firefox browser, with the release of Firefox Quantum (version 57) next month. The good news is that all the capabilities of Firebug are now present in current Firefox Developer Tools.

The story of Firefox and Firebug is synonymous with the rise of the web. We fought the good fight and changed how developers inspect HTML and debug JS in the browser. Firebug ushered in the Web 2.0 era. Today, the work pioneered by the Firebug community over the last 12 years lives on in Firefox Developer Tools.

Looking Forward, Looking Back

But before we move on, let’s take a few moments to remember all the great milestones of the Firebug project, and share some stories from early community members.

  • Jan 2006, Firebug 0.2  Joe releases the single tab console with AJAX logging.
  • May 2006, Firebug 0.4  There is a new top-level tab for JavaScript debugging.
  • Dec 2006  Firebug is open-sourced.
  • Jan 2007, Firebug 1.0  The start of Web 2.0!
  • Aug 2008, Firebug 1.2  First FWG (Firebug Working Group) release.
  • Oct 2009, HTTP Archive (HAR) One archive for web performance and beyond.
  • Feb 2010, Firebug Lite for Google Chrome released (bookmarklet).
  • Apr 2010, Dynamic and Graphical Web Page Breakpoints invented (pdf).
  • 2011Boom of Firebug extensions.
  • June 2014, Firebug 2.0 Fresh new UI compatible with Firefox Australis.
  • June 2016, Unifying Firebug & Firefox DevTools.
  • Oct 2017, Goodbye Firebug!

Firebug 0.2, Console panel

I’d like to share some of my own fond Firebug memories and historic moments, beginning with how it all started.

The very first version released in Jan 2006 on AMO is Firebug 0.2 with a short comment from Joe Hewitt:

This is a very early release – the code is only a few days old. Beware of the leopard.

Later in December 2006, Joe makes the important decision to open source Firebug:

The first announcement is in regards to Firebug’s licensing. As I was developing Firebug 1.0, I began to wonder if I should try to turn the project from a hobby into a business. When I proposed this idea on my blog, the response was very positive and reaffirmed my belief that Firebug could do well as a commercial product.
However, in the end, I just don’t feel like that is the right thing to do. I love working on Firebug because I know I’m making a lot of people happy and helping to advance the state of the art. That’s a lot more meaningful to me than just about anything else, and so, I’ve decided that Firebug will remain free and open source.

After releasing v1.0, Joe Hewitt moved on to his next adventure at Facebook and John J. Barton (IBM) soon became interested in resuscitating the project …

Oh Firebug! Fun times. I started out as a user and contributor (of obscure debugging-of-eval features). When Joe Hewitt decided to move on, I hunted around IBM to gauge interest in continuing his work. At that time, enterprise Web apps were just starting to grow without much more than ‘window.alert()’ debugging. Once Jan ‘Honza’ Odvarko joined the Firebug effort, IBM’s Rational IDE team agreed to support my work on Firebug and I created an Eclipse plugin to integrate Firebug with the product. Honza and I filled in Joe’s great framework, scaling the tool to larger and more complex applications. We added tests and improved the release vetting, then fixed bugs and responded to bug reports to build community. Soon we had other contributors and a growing collection of Firebug extensions. Mike Collins joined me to help on the product side and I collaborated with Salman Mirghasemi at EPFL on research projects leveraging Firebug technology.

I’m proud of our collective efforts to sustain Firebug during the critical growth phase of Web technology. This tool helped countless developers build sites used by millions of people worldwide. Now every browser has a debugger inspired by our work. While I miss the scrappy self-reliant teamwork of Firebug development, we leave knowing we made big positive impact.

Firebug 1.2, Net panel

The success of a project is always dependent on the dedication of developers, contributors, and involved users. But, there were also times when it wasn’t simple to keep up with the quickly evolving Firefox browser and we had to work hard.

A snippet from John J. Barton’s post (March 2010):

We’ve come along way since Joe Hewitt unleashed Firebug 1.0. Arriving at the start of the Web 2.0 revolution, Firebug helped shift people from thinking Web 2.0 was a fad to realizing Web apps can be real. Firebug had to grow up in a hurry while we still did not understand the code well and certainly didn’t understand Firefox.

Firebug 1.1 wasn’t really meant to be, though it was used by a few dedicated and helpful folks. So Firebug 1.2 was our first real release beyond Joe’s original source. Behind the scenes we had lots of extra work to close a security hole in Firebug.  At the time we could not tell anyone: too many users were exposed.

Firebug has been always very popular project and many developers started working on Firebug features, fixing bugs and building extensions. Yes, many new extensions to extend  an extension. We were all using the same technology. Community happiness.

There is a post I made about Firebug extensions, July 2008:

Have you ever been interested in what extensions are available for Firebug? If yes, take a look at what I have found. Frankly, I was quite surprised how many Firebug extensions already exists out there.

There were about 10 Firebug extensions in 2008 and more than 60 in 2011. Not easy to evolve a code base that needs to support so many extensions, trust me!

I started working on Firebug in 2007 and I joined John J. Barton when he was working on v1.2. At that time, the Firebug Working Group started and we all focused on building Firebug as well as the community around it. These were exciting times. We were relatively small group and every single new feature we introduced was used by millions of people the next day. We’d been getting great amount of feedback and learning a lot about how to build visual tools for web developers.

The first Firebug piece I worked on was the Net panel. HTTP monitoring was always my cup of tea and we soon noticed a lot of user requests to export data collected by the panel. Implementing such a feature wasn’t hard, the nice piece of work was introduction of a new format for exported data. A couple years later, around October 2009, we introduced the new HTTP Archive (HAR) format with Steve Souders (page-load-performance guru and author of YSlow, often considered the first Firebug extension) and Simon Perkins. This format was a great success and many tools support it now.

From Steve Souders post:

I suggested that, rather than create yet another proprietary format, Firebug team up with HttpWatch to develop a common format, and drive that forward as a proposal for an industry standard. I introduced Simon Perkins (HttpWatch) and Jan “Honza” Odvarko (main Net Panel developer), then stepped back as they worked together to produce today’s announcement.

I had good times working with John and others on the project. Because Firebug was well written and well-architected, it was a pleasure to build on top of it. Joe did a great job laying the foundation to support dozens and dozens of extensions built atop Firebug. John J.was an excellent manager and peer to work with. One of the concepts we invented and implemented in Firebug was related to a new kind of breakpoint. We called it Dynamic and Graphical Web Page Breakpoints. Yeah, you might know these features as Break on XHR, Break on Next, Break on DOM mutation, etc.

From Firebug blog:

Jan “Honza” Odvarko and I have submitted “Dynamic and Graphical Web Page Breakpoints” on the 1.5 breakpoints to WWW 2010.  It motivates the various breakpoints, describes the user experience and the implementation, then relates this breakpoint work to academic papers.

If you want the Cliff Notes version, we also have a demo page.

Firebug 2.0 was released in June 2014. It was a major rewrite of the UI in order to make it compatible with the new Firefox Australis theme. We delivered on time and we were proud of it, a true community achievement. Since that release, we’ve been in maintenance mode.  The latest Firebug version on AMO is 2.0.19.

Officially, we started unifying Firebug with built-in Firefox tools around 2016, but in fact the process began earlier. Mozilla’s strategy was to introduce new built-in developer tools offered as a default in Firefox. Modern developer tools written from scratch. The decision was made not to use Firebug as the platform to build upon. Some Firebug users and contributors were disappointed by this decision, but Mozilla’s infrastructure and requirements were different at that time. Sometimes it’s just better to start from scratch, which is especially true for software development.

Most importantly, today’s Firefox DevTools are in great shape and faster than ever, based on web technologies like React/Redux/Webpack, cool things. The architecture is ready to support extensions. The team is great, with experienced tool developers. This is my team.  :-)


The process of unifying Firebug with the rebuilt devtools was completed with the release of Firebug 3 (aka in 2015. This prototype was built as an extension to built-in Firefox devtools and eventually integrated directly into devtools. You can learn about how to migrate from Firebug. You can try Firefox Developer Tools by updating your release browser or downloading Developer Edition.


Support for every old-school* extensions stops in Firefox Quantum (aka 57). Yes, including Firebug and that’s why there was great opportunity to write this post.

The king is dead, long live the king!


Jan ‘Honza’ Odvarko


  • XUL & Add-on SDK based

List of contributors: Joe Hewitt, John J. Barton (IBM Almaden), Jan Odvarko (Mozilla Corp.), Max Stepanov (Aptana Inc.), Rob Campbell (Mozilla Corp.), Hans Hillen (Paciello Group, Mozilla), Curtis Bartley (Mozilla Corp.), Mike Collins (IBM Almaden), Kevin Decker, Mike Ratcliffe (Mozilla Corp.), Hernan Rodriguez Colmeiro, Austin Andrews, Christoph Dorn, Steven Roussey (Illuminations for Developers), Sebastian Zartner, Harutyun Amirjanyan, Simon Lindholm, Stampolidis Anastasios, Joe Walker (Mozilla Corp.), Vladimir Zhuravlev, Farshid Beheshti, Leon Sorokin, Florent Fayolle, Hector Zhao, Bharath Thiruveedula, Nathan Mische, Belakhdar Abdeldjalil, Jakob Kaltenbrunner, …

List of translators: Leszek(teo)Zyczkowski (pl-PL), markh (nl), peter3 (sv-SE), AlleyKat (da-DK), Hector Zhao, lovelywcm (zh-CN), Lukas Kucharczyk, Michal Kec (cs-CZ), Team, ReinekeFux, Benedikt Langens, Sebastian Zartner (de-DE), l0stintranslation, gonzalopirobutirro, Luigi Grilli (it-IT), alexxed (ro-RO), Nicolas Martin, Franck Marcia (fr-FR), gLes (hu-HU), Xavi Ivars – Softcatala (ca), gezmen (tr-TR), eternoendless (es-AR), Dark Preacher (ru), Tiago Oliveira, Diego de Carvalho Zimmermann, Alexandre Rapaki (pt-BR), Juan Botias, Alvaro G. Vicario (es-ES), Andriy Zhouck (uk-UA), Hisateru Tanaka, k2jp (ja-JP), Mohsen Shadroo (fa-IR), Eduard Babayan (hy-AM), Helder Magalhaes (pt-PT), Tomaz Macus (sl-SI), Stoyan Stefanov, Alexander Shopov (bg), Kristjan Bjarni Guomundsson (is-IS), NGUYEN Manh Hung (vi-VN), Bwah (hr-HR), Sonickydon (el), David Gonzales (es), DakSrbija (sr), bootleq (zh-TW), Asier Iturralde Sarasola, Julen Irazoki Oteiza (eu), …

About Jan Honza Odvarko

Honza is working on Firefox Developer Tools

More articles by Jan Honza Odvarko…


  1. Jens Grochtdreis

    Firebug changed everything for me as a frontend developer. Looking back I cannot remember how hard the times were before Firebug stepped on the scene.

    Now each browser has mature developer tools. That’s because of Firebug. Mission accomplished!

    Thanks a lot for your work and for your influence on all browsers.


    October 24th, 2017 at 08:32

    1. Leendert

      Yes, exactly what Jens says!

      Firebug made my job so much better and less frustrating. It’s hard to imagine working on frontend code without proper developer tools in the browser and Firebug certainly set the high standard for all dev tools available today.

      Thanks for everything! <3

      October 27th, 2017 at 02:48

  2. Fawad Hassan

    Firefox dev tools seem pretty good feature wise but they lag and get slow when used in big projects.

    October 24th, 2017 at 09:09

    1. Harald Kirschner

      After a long phase of rewrites we are heads down on making the tools faster. You can best follow along on Nightly, or if you like a slower pace, on DevEdition. You can help us by filings any slow issues that get in your way in bugzilla.

      October 26th, 2017 at 09:28

  3. Alvaro G. Vicario

    Kids, before Firebug came to change the game, all we had was… Venkman:

    It was surely great, but I could never figure out how to use it. You can’t imagine the impact it had in many of us to find a tool like Firebug. Thank you very much for imagining it!

    October 24th, 2017 at 09:40

  4. nemo

    What I miss most about Firebug (and still do) was the context menus crammed full of useful things. I still spend a lot of time hunting around in the dev tool menus trying to locate a Firebug function. Thankfully some of this stuff was improved in nightly – for example persisting network trail on redirect used to be hidden away in global config and is now on top bar like firebug.

    Here’s one I still haven’t found a good replacement for though. Firecookie. left side is devtools. right side is firecookie.

    In firecookie I got more detailed breakdown of cookie data, and could add/remove from firefox whitelist. Was definitely a nice to have. I used it both for dev and for convenient cookie whitelisting.

    October 24th, 2017 at 09:53

    1. Harald Kirschner

      Great to hear that we covered most of your cases!

      Those are a lot of options in Firecookie. Since you mentioned whitelist of blocked cookie the feature you are missing most, are you using it for browsing or development?

      October 26th, 2017 at 09:31

  5. Patrick Flowen

    Thanks for your work Jan. Firebug was thru many years my favorite firefox plug-in. It is sad that this great piece of code, and xul extensions, will be ending it’s life. I miss in devtools few things. But lets hope in the future this will at least be as good as FireBug.

    It is really frustrating, that such great browser and addons will be transformed in to tool which treating users like a dumb, that don’t need advanced functionalities in the name of becoming similar to google chrome. Not mentionig some wired privacy controversions (Cliqz etc).

    October 24th, 2017 at 09:54

    1. Harald Kirschner

      To bring back advanced functionality that power users liked so much we will experiment with additional APIs for extensions in an open way so other browsers can follow. We learned from the past, so we are putting in a lot of effort to implement them in a sane way that is fast by default.

      Let us know if anything specific is missing in Devtools!

      October 26th, 2017 at 09:34

  6. Salar

    Ok, how about fixing developer tools debugger?

    Well it is not broken but broken is a good word to describe it. To be more specific, setting a breakpoint (in different ways) is broken most of the time. You cannot disable call stack and it lags the whole debugging process. Debugger can’t show the exception location/script in dynamic loaded scripts. Debugger doesn’t show variables on breakpoints set by ‘debugger’ keyword in dynamic loaded scripts and list goes on.

    FYI these all are in bugzilla but for some reason that is expected from Mozilla they will rust there! (pun intended)

    October 24th, 2017 at 10:05

  7. gabriel

    Missing a recognition to the inspiration: IE6’s Internet Explorer Developer Toolbar!

    October 24th, 2017 at 10:11

  8. Kevin Dangoor


    You did so much work over so many years to steer Firebug through incredible change. Thank you (and the rest of the Firebug contributors) for the hard work on Firebug. And thanks for this nice trip through Firebug’s history.

    And, of course, thanks also to everyone working on Firefox Developer Tools which made it possible for Firebug to ride off into the sunset.

    October 24th, 2017 at 10:18

  9. Colby Russell

    When it came out in 2005, Firebug was the first tool to let programmers inspect, edit, and debug code right in the Firefox browser.

    Joe Hewitt released Firebug as an extension for Firefox in 2005. However, it was not the first. Every browser-based devtool today is descended from the DOM Inspector, which predates Firebug. Hewitt checked the first DOM Inspector source files in to the Mozilla codebase ca 2001. When Firebug was first released, the Mozilla apps (including Firefox) bundled DOM Inspector by default. Robert Ginda’s Venkman JavaScript debugger was around at the same time, although not bundled by default with anything except SeaMonkey. In fact, when JS debugging was added to Firebug, it worked by targeting the interfaces that had been created for Venkman, so much of the heavy lifting had already been done there. It was later that DOM Inspector got decoupled, and Firefox 3 was the first release that didn’t bundle DOMi. However, it was maintained as an extension, and for years continued to be used for things that Firebug couldn’t do, such as poking at the XUL-based DOM for the UI of FIrefox itself.

    (When the decision was handed down to create the current devtools to be integrated with Firefox 4, it was unusable for a long time, and made DOM Inspector unusable, too. Mozilla contributors who relied on DOM Inspector for nightly builds, for example, found that devtools had bogarted the DOM Inspector’s shortcut keycombo for itself to pop up a highlighter overlay that only worked on Windows. Testing and debugging nightlies were a big pain around that time, because devtools was a bad citizen—not only taking over the shortcut for a tool that wasn’t ready, but it did so by dynamically attaching listeners instead of using XUL overlays. DOM Inspector had to be patched to specifically target devtools to neuter its key listeners and take the keycombo back over in order to get a sane debugging tool.)

    October 24th, 2017 at 13:11

  10. Brian Glover

    Firebug became a standard among web developers. It gave us a tool that significantly helped create a better web experience for everyone. Thanks!

    October 24th, 2017 at 17:31

  11. Dmitry

    Thank you for the great tool. I used it since the very beginning in 2006 if not mistaken. It saved me a lot of time – console, js debugger, net tab to trace Ajax calls and grab curl commands, DOM inspector allowing changes on the fly. I still feel I used not much of the whole range of tools it provided. Always thought one day I’d spend enough time to learn all of them to more efficient.
    Great tool! Thank you for it.

    October 24th, 2017 at 17:57

  12. Guan Jyun


    October 24th, 2017 at 18:19

  13. Carter

    Thanks Firebug! you are salvation of millions of developers. It is your early expedition on the debugging tool that saved billion of hours of all developers, which is invaluable contribution to the community. Joe Hewitt, Honza, the firebug team, and all the contributors, your hard work will always be honored.

    My Best Regards to you

    October 24th, 2017 at 19:41

  14. Ernesto Butto

    I remember when I was learning to code (2000 – 2007 and still learning ) and a friend showed me fire bugs everyone was like “What? No way!! How cool and useful!” Thank you!

    October 24th, 2017 at 21:18

  15. Suraiya Aysha

    Still I like firebug so much. I will miss a lot firebug.

    October 24th, 2017 at 22:25

  16. Khizar

    Even though Firefox dev tools are in great shape. It is not easy to stop using and switching Firebug straight away ^^

    October 24th, 2017 at 23:50

  17. khizar

    Although Firefox dev tools are in pretty good shape. Its not easy to switch from Firebug though ^^

    October 25th, 2017 at 00:00

  18. Sebastian Zartner

    Firebug had a small core team behind it, nontheless it helped millions of users all over the world building and debugging their websites. With that success it had (and still has) great influence on the development tools integrated in browsers nowadays.

    It was great to work on such a great project and with such a great team!

    For everone still missing Firebug features in the Firefox DevTools, is tracking them.
    Anyone wanting to help the team behind them is welcome to do so. A guide how to contribute can be found at

    October 25th, 2017 at 01:47

    1. Alexandre Leduc

      I’m relieved to see my most missed Firebug feature is in there (Bug 704094 – Add a DOM View to the inspector)

      October 26th, 2017 at 13:58

  19. Priyadarshan Dhaigude

    Thank you Firebug Team, for offering such a great tool it helped alot
    When Plugin becomes part of application it reached to destination like a mobile app becomes OS features
    Wish you all the best (Y) for the Future Project !

    October 25th, 2017 at 03:31

  20. Nemanja Ćosović

    Firefox made a mistake letting FireBug go. Chrome and Safari have better developer tools.

    October 25th, 2017 at 04:21

  21. Monarch

    You helped me a lot firebug. When I was a beginner, you were there at every step to help me learn development. Going to miss you a lot

    October 25th, 2017 at 04:23

  22. Oana

    I have been using it since Feb 2006 (as a condition to pass we web exam!)
    11 years later I was still using it!
    Thank you Firebug! You were there for every step!

    I wish you guys all the best!

    October 25th, 2017 at 05:03

  23. Marco

    What will happen to Firebug Lite? There are environments like embedded browsers, where no other dev tools are available.

    October 25th, 2017 at 05:27

  24. Steve Souders

    Firebug changed my life. I was so hesitant the first time I met Joe and proposed integrating YSlow with Firebug – and he agreed! Then starting the Firebug Working Group – I think I’m still the owner of that mailing list. I remember that first meeting with John J at IBM. We all wanted the awesomeness of Firebug to carry on, and we made it happen. Firebug has been an integral part of growing Frontend Engineering to the preeminent role it now plays on the Web.

    October 25th, 2017 at 08:03

  25. Jian

    Thank you for firebug,and it take me into web world during fresh time.

    October 25th, 2017 at 08:51

  26. Emmanuel Espitia

    A great tool and an admirable development team, you guys are the best! Thanks a lot

    October 25th, 2017 at 10:14

  27. Zach Chandler

    Firebug was lifechanging. So awesome. Many thanks to all those hard working devs that built it!

    October 25th, 2017 at 15:05

  28. YongWoo Jeon

    Thanks. Firebug!

    October 25th, 2017 at 21:46

  29. Jon Humphrey

    Thank you Firebug for helping us all make a better web for everyone! :-D

    October 26th, 2017 at 03:33

  30. Afterbanks

    Say goodbye too to Firepath and firefinder

    October 26th, 2017 at 03:37

    1. Emil Petkov

      These two are certainly the most missed now by me too. Especially Firefinder…

      October 26th, 2017 at 11:28

  31. Umar

    I am gonna miss Firebug!

    October 26th, 2017 at 05:21

  32. CG

    Ugh, the transition to FF Dev tools has been painful, to say the least, and right in the middle of a project. I’m glad we have a place to get together and share our pain. That said, the stuff FF Dev tools is doing for CSS grid has been pretty interesting. To the future!

    October 26th, 2017 at 07:11

  33. Eliazer Braun

    RIP you where my inspiration and my many web dev first AHA moments..

    Thanks you so much!!!!!!!!

    October 26th, 2017 at 07:52

  34. Steve Horn

    Firebug was my guiding light through years of growth as a developer. Always my preference tool. But not Firefox Developer (v57) is my new guide. So far, so-so-so Good!

    October 26th, 2017 at 09:29

  35. Saroj

    Firebug is still better than Firefox’s inspector

    October 26th, 2017 at 09:31

  36. Ali

    FireLive! The best development tool!

    October 26th, 2017 at 09:33

  37. ahsan

    fire bug is soo important that i didnt install any update after 49.0

    October 26th, 2017 at 09:38

  38. Mario

    A true pioneer. Thanks for all the help over the years, and the rich legacy you leave on all browsers.

    October 26th, 2017 at 09:39

  39. zian974

    RIP firebug.
    La première extension qui m’a permis à l’époque d’enfin apprécier développer en javascript.
    Sinon, quelle galère c’était …

    October 26th, 2017 at 10:29

  40. Megan

    I got a job at a marketing agency doing super remedial QA testing on newly built websites in 2008. I had a little basic HTML knowledge from a single class I took (and of course from editing my MySpace page).

    One of the devs showed me Firebug so I could help fix small display issues.

    I’ve been working as a front-end dev for seven years now. I wouldn’t have a career if not for Firebug. Thanks, lil buddy.

    October 26th, 2017 at 11:06

  41. Sayed

    We miss you lots and love you… Firebug.

    October 26th, 2017 at 12:17

  42. Mohit lodha

    Firebug was lifechanging. So awesome. Many thanks to all those hard working devs that built it!

    October 26th, 2017 at 13:18

  43. Joel Marchesoni

    Firebug helped me realize my goal of doing my design work in the browser, so I could create and tweak using code instead of pixels.
    Then after I’d coded the app from the mockups, it was a part of the debug workflow as well.
    While I’m sad to see it sunsetting, I appreciate every day that it paved the way for the integrated devtools in Firefox.
    …Wow, I got more emotional there than I expected!

    October 26th, 2017 at 13:41

  44. Jeffery

    I’m going to miss Firefox because I’m not giving up all the really useful add-ons that I use on a daily basis. A lot of my Add-ons the developers can’t convert to the new system.

    I am sad Firefox is going this way. I’ll use 56 for as long as I can then probably switch to chrome which I’m not a huge fan of either.

    October 26th, 2017 at 13:53

  45. Klwood

    Firebug was/is THE premier web development tool, and great thanks and kudos to everyone who worked on it! It changed my life as a developer and solidified my decision to go into web development. Before it, front end debugging was an endless list of “alert” statements lol. I am very sorry to see it going. I have known about this for a while, and tried to warm up to the dev tools, but they are still not a worthy replacement, IMHO, for Firebug. One of the biggest things I miss is the ability to edit CSS or HTML on the fly, and see the changes rendered dynamically in the page you are viewing. A great example is working with bootstrap layouts : in Firebug, if I go into the HTML tab and change the column values, I instantly see the changes in the layout of the page – not so with the dev tools, at least not last time I looked. I guess I will have to accept the change, but I am actually using an old version of FF now (49) and disabling updates so I can still use Firebug. That’s how much more I like it than the dev tools. Hopefully, they will eventually get all of the features baked in that made Firebug so beloved.

    October 26th, 2017 at 15:40

  46. Edward Dolloso

    Hope to enjoy using the new technology of firefox

    October 26th, 2017 at 16:24

  47. David

    Thank you firebug for all these years.

    October 26th, 2017 at 19:02

  48. Kesavan Muthuvel

    Thank you Firebug & the wonderful team! you are primary reason for most websites rendering as expected. Love you. Swiss-knife of the development team.

    October 26th, 2017 at 20:38

  49. Ian V

    Thank you Firebug! You help me in all those nights I’ve been making WP themes.

    October 26th, 2017 at 22:35

  50. chrqls

    Thanks Firebug for making my dreams come true :3

    October 27th, 2017 at 01:52

  51. Asanka Dewage

    This was a life changing tool. It was simply unbelievable back then. What we take for granted today evolved from Firebug. Even though I don’t use Firebug anymore, this news makes me sad. This used to be our saviour! Editing CSS on the spot with the creative director sitting next to me.. man, it saved many hours of going back and forth… can’t believe that was 10 years ago!!

    Thank you Firebug! Thanks to all developers who contributed to make this happen.

    October 27th, 2017 at 06:04

  52. rctiqq

    Thank You So Much FIREBUGS T_T

    I Hope after quantum u can reborn again :D

    October 27th, 2017 at 06:26

  53. Phil

    Echoing most of the sentiments above: Thank you to anybody who worked on developing Firebug – you made our lives easier as developers. Your efforts are very much appreciated

    October 27th, 2017 at 07:24

  54. Peter

    Please bring it back. Please!!

    Its soo much better than the native debug tool

    please someone make a fork and bring it back

    October 27th, 2017 at 08:56

  55. Kevin McNeely

    I have been working with Firefox since version 2 and I am still not disappointed.

    October 27th, 2017 at 14:04


    Thanks and Goodbye to Firebug

    October 27th, 2017 at 18:28

  57. Fernando Boaglio

    Great post, we all love Firebug, let’s hit F12 and have one minute of silence.

    October 27th, 2017 at 18:38

  58. Camilo Martin

    I’m kind of sad the technology that allowed for Firebug to exist is being phased out. Sure, we got to experience Firebug and all the “developer tools” from various browsers now have the same features, but what if the world was always Web Extensions-based?

    If Firefox wasn’t hackable from the start, we would never have seen Firebug. We wouldn’t even know it could be so good, it wouldn’t be a fond memory. A world with only a monolithic, “safe” and constrained Web Extensions may be a world without the next Firebug, and that makes me sad.

    October 27th, 2017 at 19:38

  59. Michael

    Let me also chime in. Firebug was a real lifesaver, and probably the number one reason I got Firefox installed around the workplace. Great job then, and also now with the Firefox DevTools. Keep it up!

    October 28th, 2017 at 06:59

  60. Dan

    I’m sad to see Firebug go!

    Although I’m excited about Web Extensions I still have a (company internal) Firebug Extension which I cannot get feature parity with the current Web Extensions implementation (even in Nightly) until more of the Dev Tools APIs are implemented :( I do appreciate all of the efforts but it’s a slow road to compatibility with Chrome.

    October 28th, 2017 at 23:04

  61. Jawad

    Really, miss Firebug, it is made by developers for developers, so smartly made!!
    honestly my productivity as a developer dropped a bit down without such an amazing dev tool.

    October 29th, 2017 at 10:07

  62. Aslam

    I feel sad and excited.

    Great work guys you saved millions of hours of developers around the world.

    Hats off to the contributors.

    October 29th, 2017 at 22:49

  63. Crystal Joy Du

    Hey! I like the way the new firefox integrated the web development tools.

    October 30th, 2017 at 02:01

  64. Tanveer

    Firebug not only influenced every single browser out there, it also helped me get into web development. Massive congrats to the devs, we should do a little fundraising for them or something.

    October 30th, 2017 at 02:49

  65. Kemal Okrali

    Man, this is some sad news, i had a lot of time with firebug, it helped to enter the web dev.

    Kemal Okralı

    October 30th, 2017 at 06:58

  66. Alex

    It says 70 comments at the top but I can only see 14 on the page with no link to older comments. Is this a bug?

    October 30th, 2017 at 12:47

  67. meepo

    God no !

    October 30th, 2017 at 20:24

  68. B K

    B Y E

    October 30th, 2017 at 21:28

  69. Mallesh Tirugudu

    I feel sad to see Firebug go!!
    I have been working with Firefox since 2010 and I am still not disappointed.

    October 30th, 2017 at 21:44

  70. Indy

    So long and thanks for all the fish!

    October 30th, 2017 at 22:42

  71. Chetan

    Awww, Its sad news. I have been working on this since 2006/07. Life saver for me on many cases. Thanks very much. I agree with Tanveer on Fundrising.

    October 30th, 2017 at 22:47

  72. Daniel

    Really sad to see it go. So far there are a lot of little things that firebug did much better than the native debug tool. (most notably it made/showed edits to the markup as you were changing it, not after clicking away.) I actually reverted back to an older version of Firefox temporarily just so I could use it again.

    Hoping that the native tool keeps getting better.

    Thanks for a great tool!

    October 31st, 2017 at 09:57

  73. Gopal Chaladi

    Firebug is always be my first love. As a font end developer I always thankful to it. A friend, a life saver and life changing for so many as mine. Thank you for developers, who shown the future of all web browsers.

    October 31st, 2017 at 14:28

  74. Dave Lee

    Firebug is one of those tools that I can’t imagine being without. Great work – be very proud of what you’ve done.

    November 3rd, 2017 at 01:28

  75. Alex

    Thanks for great job! Thanks for FireBug!

    November 3rd, 2017 at 17:17

  76. Edwin Shang

    Create project and thanks a lot for your effort! Firebug is a division of new web developing era. I will always remember it for sure.

    November 5th, 2017 at 18:26

Comments are closed for this article.