ItвЂ™s very disconcerting to have to read ordinary log messages in red. IвЂ™m seeing this problem in all the themes, including the Firebug theme, so thereвЂ™s probably some underlying issue that affects all of them. Obviously it should be the other way around. Right now the ConsoleвЂ™s ordinary log text appears in red, and the alert/error text in black. ThatвЂ™s the single biggest annoyance for me. Your list of вЂњmost importantвЂќ items here doesnвЂ™t mention font color. Is this available now in Firefox 50.1.0? December 20th, 2016 at 07:15 Sign up for the Mozilla Developer Newsletter:

articles by Patrick BrossetвЂ¦ Discover great resources for web development.

Patrick manages the DevTools engineering team at Mozilla Honza is working on Firefox Developer Tools Sole works at the Developer Tools team at Mozilla, helping people make amazing things on the Web, preferably real time. The Firefox DevTools and Firebug teams About The Firebug spirit lives on in all of the browser developer tools we build and use today. We thank you for your loyalty and hope you understand why weвЂ™ve made this difficult decision. An option to add cookies: ( bug 1231451 and bug 1231452).Font-size changes in the Firebug theme ( bug 1319079).A DOM properties sidebar panel ( bug 704094).Validating CSS values and selectors as you type: ( bug 1227054).Improvements to the way console log messages are displayed: ( bug 1032855, bug 1165010 and more).Live previewing changes made in the inspector (when changing attributes or editing as HTML: bug 815464).An events sidebar panel: ( bug 1226640).Various console auto-complete improvements: ( bug 1267140, bug 1270015, bug 672733, and more).Better CSS auto-completion (like bug 1106336 and others).We are already tracking missing features on this bug, and so far you have told us that the most important are these: Or, post to this discussion thread on Twitter.Share your feedback on this thread on the Firebug Google group.Comment on this thread on the Mozilla dev-developer-tools mailing list.You can help: Tell us which features you need are missing. We understand that disruption is never really welcome, but we are working hard to ensure developers have the best possible tools, and sometimes this means we need to refocus and use resources wisely.

If you are switching now from Firebug to Firefox DevTools, you will of course notice differences. Also, over 40 bugs were fixed to close the gap between DevTools and Firebug.ДЇor curious readers, a couple of articles on and on the Firebug blog go into more detail. Several features have been absorbed: The DOM panel, the Firebug theme, Server-side log messages, the HTTP inspector (aka XHR Spy), and various popular add-ons like FireQuery, HAR export, and PixelPerfect. Other Firebug Working Group members like Sebastian Zartner and Florent Fayolle are also active DevTools contributors.ДЄ huge thank you to them for bringing their expertise in browser developer tooling to the project! In practical terms, what does it mean to merge Firebug into DevTools? Many of FirebugвЂ™s core developers are on the DevTools team, including Jan вЂHonzaвЂ™ Odvarko and Mike Ratcliffe.

The decision was made that the next version of Firebug (codenamed Firebug.next) would build on top of Firefox DevTools, and Firebug would be merged into the built-in tools.ДЄnd perhaps most importantly, we joined forces to build the best developer tools together, rather than compete with each other. Additionally, FirefoxвЂ™s built-in developer tools have been gaining speed, so it made sense to base the next version of Firebug on these tools instead. The Firebug Working Group agreed they didnвЂ™t have enough resources to implement such a massive architectural change. Unfortunately, Firebug wasnвЂ™t designed with multiprocess in mind, and making it work in this new scenario would have required an extremely difficult and costly rewrite. With multiprocess architecture, if a website crashes, it doesnвЂ™t also crash the whole browser. ElectrolysisвЂ™s multiprocess architecture makes it possible for Firefox to run its user interface (things like the address bar, the tabs and menus) in one process while the content (websites) runs in other processes. The reason for this huge change is Electrolysis, MozillaвЂ™s project name for a redesign of Firefox architecture to improve responsiveness, stability, and security. As you might have heard already, Firebug has been discontinued as a separate Firefox add-on.

Install firebug on firefox