[t-writescode]

I'm a relatively new web dev and I've been quite happy with Firefox's Web Dev tools. What does Chrome's dev tools give someone that Firefox's doesn't? I can edit css on the fly, see where a css rule is being overwritten, debug javascript, etc.

[arealaccount]

FF dev tools just don’t work sometimes, notably with iframes, sometimes with source maps, and other edge case types things.

I use FF for 99% of dev, open Chrome maybe once a quarter. It’s a better browser.

[paulryanrogers]

Funny, I find Chrome Dev tools doesn't save some response bodies, while Firefox consistently does.

[politelemon]

I use FF but Chrome's dev tools have a lot more going for it including memory profiling and performance tools. On the other hand, Chrome's network panel is awful and it's a chore to see the domains and full URLs involved.

[nine_k]

One an develop in FF, but has to test in Chrome. (Same with developing in Chrome and also testing in FF.)

[elendee]

firefox doesnt have Workspaces. I do 100% of my CSS in Chrome Workspaces

[1718627440]

What do Chrome Workspaces have, that Firefox Profiles don't have?

[elendee]

Workspaces allow you to give Chrome permission for read / write access to given folders. You just set it once per project and then Chrome remembers.

Basically, you can press "ctrl S" for save, straight from the dev console. In FF, you have to manually designate the save location each time. It may seem like a small thing, but it's an entirely different workflow.

For frameworks that don't use plain stylesheets, it may not be useful.

[t-writescode]

I use vite, so I think I get that functionality without needing Chrome? ... if I understand what Workspaces are?