News for hackers. Stuff that matters.
Re:Google sets burial date for legacy Chrome Extensions, fea... by hutzlibu on Tuesday September 28, 2021 @04:27AM (#28680482)
"Firefox as a browser, especially dev tools, seems better in every day use than Chrome does. "

Cannot confirm at all. I do not know any feature in ff dev tools I am missing in chrome, but the other way around lots of it.

Mainly: editing and saving directly in the debugger!

Could also be my ignorance, but I regulary do debugging in FF and it works, but way less efficient.

Meaning I browse with FF, but work with chrome.

Re:Google sets burial date for legacy Chrome Extensions, fea... by yfkar on Tuesday September 28, 2021 @05:11AM (#28680718)
One thing where I've used Firefox devtools instead of Chrome is when debugging font usage (which is not very often).

Chrome tells you the used font for a single element on a pretty generic level, e.g. "Lato — Local file" or "Lato — Network resource".

Firefox Inspector has a Fonts tab that lets you list all the fonts used on a page. It tells you a more specific font name, e.g. "Lato Regular", the relevant @font-face rule and also the font URL if it's a network resource.

Re:Google sets burial date for legacy Chrome Extensions, fea... by maddyboo on Tuesday September 28, 2021 @04:47AM (#28680598)
I mostly agree, but one really nice feature FF has is the ability to see a diff of the CSS properties you've changed in the inspector:

https://developer.mozilla.org/en-US/docs/Tools/Page_Inspecto...

Re:Google sets burial date for legacy Chrome Extensions, fea... by marcosdumay on Tuesday September 28, 2021 @10:47AM (#28683456)
> Mainly: editing and saving directly in the debugger!

Hum... Firefox does that. I know because every time I mistakenly start saving I ask what is the point of it. But well, looks like it's useful for somebody.

Re:Google sets burial date for legacy Chrome Extensions, fea... by hutzlibu on Tuesday September 28, 2021 @02:50PM (#28686103)
Erm, it can edit and save code live in a debbing session?

Also, how can I edit code? It is non editable for me.

Re:Google sets burial date for legacy Chrome Extensions, fea... by marcosdumay on Tuesday September 28, 2021 @03:12PM (#28686284)
The Firefox developer version¹ has a full file menu on its code viewer, with save, open, refresh, etc.

I believe you can activate it on the main build too, but I don't know how. Anyway, if you are debugging code, I highly recommend the developer version.

1 - That is a different configuration of the same code as the main build, for web developers. It's not for developing Firefox itself.