I generally agree. The primary thing I find myself going back to Firebug for is debugging ajax calls, since I get the fully expandable request / response info inline along with console output. Chromium can show that an ajax call was made inline, but the link goes to the Network tab, and unfortunately doesn't auto-select the referenced call.
I upvoted you because I agreed; AJAX was what I went back to Firefox for.
However, a different comment in this thread mentioned the Chrome Developer Tools preferences (a little gears icon in the bottom right corner), which I'd never noticed before.
Sure enough, clicking it revealed the options 1) Log XMLHttpRequests and 2)Preserve log upon navigation. Checking those (which were unchecked by default) gave a HUGE amount of info on the AJAX calls that I just tested.
Maybe it's not what you're talking about, but it was a big find for me.
You can set it to add a line to the log when ajax calls are made, and fortunately a trace for where they are made from, but you have to go to the Network tab and click on the actual request to see the details. Clicking the link within the console output provides will take you to the tab, but not the request.
It's close - but not quite there. I prefer having it all in one place, but just having the link lead to the actual Request on the Network tab would be great.
I often have the network panel split with console, which gives access to everything. You can limit the network calls to XHR as well if that's all you're looking for.
