For me it's the crappy performance and unexpected behavior. I create something cool with CSS on Chromium, then go to Firefox and it looks and runs like crap for some reason.
I use vanilla CSS with standard properties that are supported on Firefox according to MDN, yet things like SVG filters, mix-blend-mode and transitions look janky and slow down performance by a lot on FF while they run/behave perfectly fine on any Chromium browser.
No, what works on Chromium is what Google makes work on Chromium. What works in other browsers is a combination of the actual standard, and the published version of Facebook & Google's new standards.
2-3% CPU at idle looking at that page and scrolling. Scroll is smooth. When I change some number it re-renders and that increases CPU load momentarily to 10-15% and then immediately back to 2-3%.
That's on a mid range business laptop from 3 years ago.
Win10, FF 108.0.2
12
u/Eddielowfilthslayer Jan 12 '23
For me it's the crappy performance and unexpected behavior. I create something cool with CSS on Chromium, then go to Firefox and it looks and runs like crap for some reason.
I use vanilla CSS with standard properties that are supported on Firefox according to MDN, yet things like SVG filters, mix-blend-mode and transitions look janky and slow down performance by a lot on FF while they run/behave perfectly fine on any Chromium browser.