They seem to be focusing 100% on making dom/css editing pretty but forgetting all about javascript and requests/headers etc. What gives? While this 3D dom stuff looks neat, doesn't make me want to switch from Chrome at all because it's not going to add anything to my day job which does involve DOM/CSS, but also heaps of javascript as well.
Well, the Firefox dev tools team also shipped the new Web Console and JavaScript Scratchpad in recent releases [1] and has been improving them rapidly. They've already landed much of the back-end code for the new JS debugger protocol [2] which will eventually culminate in a complete new debugger including features like remote debugging of Firefox for Android. They've also been working with the Firebug team on improved stability and other enhancements.
Today's announcement for Firefox 11 is just about the stuff that happened to ship during the most recent six-week release cycle. It doesn't mean that the team isn't working on lots of other projects [3].
Woah there, they aren't finished with their development tools. They aren't forgetting anything. They just aren't finished yet. And it's not like Firebug suddenly doesn't work anymore.
For example, you have the scratchpad, the error console, and the web console.
This is a bit older, but I see the reason they aren't trying to replace Firebug is that their is no immediate need to. They can explore do things that Firebug isn't doing.
