I don't no, just regular F12. Sadly, I still find Chrome to be much easier to work with for dev than Firefox. Firefox has made great progress lately with the d

I don't no, just regular F12. Sadly, I still find Chrome to be much easier to work with for dev than Firefox. Firefox has made great progress lately with the devtools, and the new bits like Grid Inspector are awesome, but it's sad the basics still aren't there. It's the little things... Firefox still displays cryptic JavaScript errors with internal stack traces, whereas Chrome gives clear explanations and always links the stack to a line in my code. That's just one example, none of the issues I have are anything major really in isolation, but together, I find Firefox less efficient to dev with than Chrome. The sad thing... I really, really wish this wasn't the case, because it unfortunately reinforces the point made in the article. Despite all my best intentions, I do end up building for Chrome first. I loathe and resent that but it saves me time overall. Every new release I try Firefox tools again though and I'm confident they're going in the right direction... hopefully in another few months, I'll be able to report back and confirm I use Firefox as my primary dev browser too.