There are plenty of paper cuts due to the differences of funding between Firefox and the other browsers. IndexedDB and ContentEditable are both a bit more weird and buggy in Firefox than in Chromium. Often when I release a new feature, we find out it’s buggy in some old version of Firefox on a specific Linux distribution that’s doing something a little odd to Firefox’s source code or build process.
Re:Ask HN: Can Firefox be revived?
by fragile_frogs on Friday October 22, 2021 @04:01PM
(#28961985)
Zoom on Firefox only has the speaker view, if you want to have the grid view to see everyone you'll have to use Chrome/Edge.
I also have to use Figma on a daily basis and the there are some odd things happening in Firefox that don't appear in Chrome/Edge.
Zooming in web browser is using the computer wrongly (TM). Just as using terminal or VDI client in web browser. It's wrong because security sucks, and bloat gets even bigger. These activities should be done through separate and well restricted dedicated applications.
Re:Ask HN: Can Firefox be revived?
by computerfriend on Saturday October 23, 2021 @04:55AM
(#28966787)
Using the Zoom client is also using it wrongly, because you have to install some blob from an untrustworthy company that has historically been riddled with security bugs.
Re:Ask HN: Can Firefox be revived?
by __turbobrew__ on Friday October 22, 2021 @03:04PM
(#28961238)
Slack calls and Microsoft teams calls (you can attend meetings, but cant share your audio/video) don’t work in firefox.
For my day to day use everything works fine. I don't remember anything that didn't except the vscode.dev thing that appeared in the front page yesterday. Apparently the local file access is not supported/enabled in Firefox yet.
And when I was messing with CSS a few months ago there was... background-blur? Or something like that, not supported in Firefox. But pretty minor things.
Don't remember anything else where I had to switch to chromium lately.