3 ms·
What about Chrome's F12 debugging? I miss that when I use Firefox.
by quickthrower2 7y ago
What about Chrome's F12 debugging? I miss that when I use Firefox.
- robin_reala 7y agoDepends what you’re doing. Firefox’s dev tools are definitely better at CSS debugging for example.
- tannhaeuser 7y agoIndeed. I always wondered why folks praise Chrome devtools which are pretty meh at CSS.
- iforgotpassword 7y agoAs a non-webdev to me they look pretty much identical. I only ever need them for a one off static site or some jQuery, or when trying to figure out why some page looks broken.
- jdnenej 7y agoI find the FF Dev tools to be much better but they don't have a way to inspect web sockets which I don't use but if you do.
- robin_reala 7y agoNightly can inspect WebSockets now.
- quickthrower2 7y agoOk I might be suffering from bias due to familiarity. I'll give FF more of a fair shot for debugging.
- dcbadacd 7y agoTry debugging CORS, CSP or SRI failures in FF. Much much more painful.
- rchaud 7y agoA minor quibble I have with Firefox's Dev Tools is that in Responsive Design Mode, there's no way to simply select "Fit to screen" as a Zoom level. If you're on a laptop, you'll have to scroll to see the full emulated viewport. I think touch recognition is better on Chrome too, as sliders and other touch-sensitive UI elements feel a bit more laggy in FF. On mobile, I'm happy using Brave, which is Chromium but allows you turn off scripts if you want to (goodbye autoplaying videos). On desktop, FF all the way. Except when I need to use Dev Tools.