3 ms·

I've had trouble with them. They don't include inline stack traces for errors, so you have to do a lot more digging to find what happened and where. Also, in th

I've had trouble with them. They don't include inline stack traces for errors, so you have to do a lot more digging to find what happened and where. Also, in the Network panel, every refresh resets your filters so you have to select XHR every time if you don't want to see a bunch of .html/.js file requests (this may have been fixed in FF v30, haven't tested yet). There are just a number of really small issues other than those that when you add them up, make the dev toolbar a lot less useful than Chrome. That said, I like Firefox the browser much better than Chrome.

danford 12y ago
> stack traces Starting in Firefox 31, the console will display a full stack trace for errors https://developer.mozilla.org/en-US/docs/Tools/Web_Console https://developer.mozilla.org/en-US/docs/Tools/Web_Console If you're using nightly you already have had a lot of features like this for a while. I find the dev tools in nightly a lot more useful than those in chrome and I prefer the way the dev tools are layed out in nightly. I also like the responsive design view, GCLI, and the eyedropper.
rafael-rinaldi 12y ago
Same thing for me. I use Firefox as my main browser and I think it's far better than Chrome, but its native developer tools are just very confusing so I'm sticking with Canary as my development browser.