I think part of this discussion needs to be that Firefox, while open source, doesn't provide footing for the community to build browser forks the way Chromium does. This sort of open usage, ironically, feels very fitting to the spirit of Firefox, but they're not even close to Chrom(e|ium). I've been building a browser full time the past year+ (synth.app) and FF core wasn't really even an option. They've done very lit…
> ... weird chromium only behaviors that websites rely on these days to do things (and egregiously so if they detect an agent remotely resembling chrome). This sounds like the IE6 disaster all over again.
The gnarliness spans the whole stack. From weird java-applet like API escalation behavior if chrome is detected (e.g. Google properties feature gate a ton around this) to how there is not even a clear way to get a DRM license for a custom browser without waiting for Google indefinitely [1].
Here's a challenge: fire up a chromium fork and get it to run a relaxed DRM website like Netflix. If you get that far now try loading HBOMax with their fingerprinting/DRM protection on top. I'm not even sure it'd be possible in FF (at least without some DRM piggy backing if there isn't one).
[1] https://blog.samuelmaddock.com/posts/google-widevine-blocked...