What is the perceived problem, then? 99% of sites these days are all built with kits that support Firefox just as well as Chromium, the dev choice to not support or intentionally lock out Firefox is either just laziness (not wanting to deal with any potential problems or not given enough time to run full Firefox user tests) or incentive driven (middle manager has word from high manager that they can't support firefox because highest manager makes bank from Chromium).
The technical limitation isn't actually there in the modern web, it's almost always a manufactured limitation. I think I've only ever encountered a single website that didn't actually technically work on Firefox, and that was Weather Underground. Which they ended up fixing after 3 months or so.
[...]it's almost always a manufactured limitation.
Doesn't that sound like a good description of a problem?
I think I've only ever encountered a single website that didn't actually technically work on Firefox[...]
There's gonna be a hell of a lot more of them, buddy. You're gonna have to hang your cat on your balcony to get an estimate of future weather if you want to avoid using one of them how-are-these-even browsers.
Imagine yourself as a homosexual man in Iran (should be easy). Would you say that hiding that big part of you from everyone and even go as far as marrying a woman you don't even like just not to arouse suspicion makes the problem disappear? Just the fact that you need to spoof your useragent to view a shitty website, the developer of which would (should) die under a car one day 🤞, is a solid proof that you will soon be that homosexual man in Iran.