> dev tooling still leaves A LOT to be desired.
Anything specific?
Feel free to file bugs, we want to make it better :)
https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&c...
Anything specific?
Feel free to file bugs, we want to make it better :)
https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&c...
I see a lot of these things landing in the FFs landing in the last week, so I can't commend those efforts enough. Literally, I don't want to have to ever install Firebug; it makes the browsing experience even more sluggish. And I would have probably never started using FF, a decade ago, if it wasn't for the tooling, and I would have never had a chance to convince as many friends and family to use FF. The same reasons I will just recommend Chrome, today.
Frankly, you will have to have something that Chrome doesn't to bring us back, and it's been a long time coming for the tooling to be even on par. Again, I commend your efforts, because I think your community involvement and dev blogs are really great.
(I keep development separate from regular browsing, either through Incognito or separate Firefox profiles. This way, my regular browser addons don't distort my view of how-my-website-looks-to-most-people, and Firebug speed becomes irrelevant.)
Just a note, we use bugzilla for everything, so if there is ever a specific feature you want, you can make a bug for that feature. For example, "integrate source maps with the debugger" was the title of a bug that I worked on.
One thing that irks me is inspecting returned JS values - I almost never want to see [object Array]. I vastly prefer the Chrome dev tools output: inline, expandable, and a meaningful representation for objects.
Not a bug, but I think it would be a big improvement :)
BTW, we use bugzilla bugs for features too, so if you feel there is a specific feature missing, just open a bug for it.