The one thing I always liked about Chrome dev tools was the ability to introspect WebSocket frames. Last I checked this couldn’t be done in Firefox :(
Otherwise, I have found Firefox dev tools to be fairly competitive. I liked the CSS Grid stuff they had around the launch of Quantum; it made it easier for me to jump into Grid.
I use Firefox personally, but develop with Chrome. I have a hard time getting stack traces from Firefox reliably. Oftentimes one of the following occurs on Firefox:
There is no error, but the page won't load.
There is an error, but the error message is generic.
There is an error message, but no stack trace.
When I switch to chrome, I always get the error and stack trace without any further code modifications.
I make sure to clean up for Firefox in releases. But it's just impossible to develop without error messages and traces. I'm on Ubuntu using the latest stable releases.
Ugh. Is this really still broken? I'm not a web dev but I remember having to switch to Chromium 6-8 months ago when I needed to debug a websockets issue.
Otherwise, I have found Firefox dev tools to be fairly competitive. I liked the CSS Grid stuff they had around the launch of Quantum; it made it easier for me to jump into Grid.