I agree, that's the single feature that's always kept me loyal to Firebug. There's a bug open on that at: https://bugzilla.mozilla.org/show_bug.cgi?id=972655

I'm attempting to find time to assist with it, but haven't thus far. Perhaps throwing it out here will bring in additional assistance

AFAIK, the built-in developer tools in FFox > v33 log ajax calls now.

Personally I've switched back to dev tools in the developer edition, mostly because the ability to see which elements have events attached from the markup view is very useful.

Logging to the console with Firebug 3: http://cl.ly/image/0V1x2g253J3F/Image%202014-12-03%20at%202....

I'm aware of that but it logs everything without a way to filter (unlike the network tab)

Hmm. What's the use case for ajax calls in the console instead of just switching to the network tab? Convenience?

Yeah. Why make people switch? Almost every app does ajax calls, so it's very useful to have that information there for almost every developer.

yes convenience, saves time switching back and forth. chrome didn't have this feature either but they recently added it (even though not as good as firebug's since when you click on the entry in the console it takes you to the network panel and hightlights the entry rather than opening it up automatically)

Firefox dev tools most certainly do log ajax calls to the console. I just tested it in 34.0.5…

I am on v35 and it doesn't. It allows you to log all network events which fills up the console.

Hit the little arrow next to it. You can select Errors, Warnings, and Log. Log makes xhr network requests show up in the console (just like the network tab). I don't know what you mean by "fills up the console".

what version are you on? I'm on 34.0, and they show up in the network tab.

Network tab isn't the console though