45
Degoogle Chromium help
(lemmy.ml)
A community for those that would like to get away from Google.
Here you may post anything related to DeGoogling, why we should do it or good software alternatives!
Be respectful even in disagreement
No advertising unless it is very relevent and justified. Do not do this excessively.
No low value posts / memes. We or you need to learn, or discuss something.
!privacyguides@lemmy.one !privacy@lemmy.ml !privatelife@lemmy.ml !linuxphones@lemmy.ml !fossdroid@social.fossware.space !fdroid@lemmy.ml
This is more common than you think. It's usually not broken entirely, but firefox constantly breaks styling/css stuff on websites I use and build. I've had a few sites ask me to switch browsers because firefox doesn't support x y or z feature too
edit: for example, WebGPU support is currently lacking in FF https://github.com/gpuweb/gpuweb/wiki/Implementation-Status
I use firefox, but I'm not blind to its few problems
Never noticed an issue and if websites using only chrome supported features, it's an issue with the website, not the browser.
That's one way to look at it. If a website works perfectly on chromium, but not firefox, why is this the website's fault?
Because in web development there are compatibility tables of what features work with which browser. If a developer has used a feature poorly supported, they either haven't done their homework, or intentionally made that call.
In web development, most reputable Front End Devs would not choose bleeding edge, barely supported features even if the temptation was there because the user comes first. Generally, you wait until it has been adopted by the main browsers (chrome, safari, ff).
Frankly, if something doesn't work in Firefox, thats like <5% market share. Probably lower for a lot of segments. I am familiar with webdev :) Let's not pretend most devs are checking caniuse for everything. Some sites leverage bleeding edge stuff that necessarily requires chrome, which is also fine. IRL people don't optimize for Firefox and that's usually okay, but sometimes there are quirks. That's all I'm saying
Not perfectly optimised is fine, but non-functional isn't acceptable. I've never seen a quirk personally, and quirks aren't a good reason to help maintain Google's monopoly on web standards.
You may say less than 5% is fine, but it could be the margins in a low margin industry. 2% could be 40% of the profit.
I haven't seen a team operate where a senior isn't checking it.
Usually the bleeding edge stuff is used by small companies trying to establish themselves because they have nothing to lose and no reputation to protect.
Plus, when you got Browser Stack, you catch a lot of problems like this.