I don't understand this because I have used Firefox exclusively since it first came out and never run into broken sites. What exactly are these exotic sites you are visiting that break in Firefox? You mentioned an elusive government website but I have used many (IRS, SSA, Edu, etc...)
>What exactly are these exotic sites you are visiting that break in Firefox?
In my case, an example of a non-exotic site is Youtube streaming 4k 60fps videos. I tried with latest Firefox a few months ago and it was still stuttering and glitchy. But Chrome plays smoothly with no issues. I previously mentioned that 4k playback has been a long-standing issue: https://news.ycombinator.com/item?id=28783904
On one hand, my computer is fairly old ... but then again, Chrome works fine on that same old hardware.
Never seen this; however, youtube prefers pushing VP9 over H.264. Maybe your computer cannot use hardware decode for VP9 and can for H.264? (Since you mentioned, it is an older one). Maybe the h264ify extension would help.
What firefox cannot do and chrome can is HDR playback.
> however, youtube prefers pushing VP9 over H.264. Maybe your computer cannot use hardware decode for VP9 and can for H.264?
No, even if I download the 4k 60fps file using yt-dlp with forced h264 codec settings locally to my harddrive, Firefox still can't play the mp4 file smoothly.
So it's not really a streaming issue or h264 vs VP9 codec issue. The Firefox core engine doesn't seem optimized to playback 4k and 8k high-frame-rate videos with low cpu utilization. Even VLC for 4k and 8k isn't as smooth as Chrome. I don't know what the Chrome team did but they really optimized that code path to play back hi-res videos.
Interesting, I recently had the opposite experience. Wanted to enable hw decode on an older Intel system and only got it to work on Firefox. Tried several different instructions from the web on how to force chrome to ignore any blacklists for drivers or anything, but still no luck.
Oh and a while ago I noticed (on a more modern system) that enabling hw decode makes chrome ignore the aspect ratio of the video and displays it like the pixels are square. Again Firefox handled it fine.
(Linux, h264 in both cases)
YouTube is routinely broken for Firefox, especially when navigating around in places like shorts. I actually find this to be a feature because it prevents me from continuing to mindlessly consume. But it is broken.
Elusive to you, essential to people living in my country. (You can't do your taxes without it.)
And look no further than Google themselves: https://labs.google.com/search/install
Maybe that explains it, I don't use Google search at all. I do use gmail/youtube however.
That's a very arrogant attitude.
I'll give you one example: I sometimes can't open OpenAI API documentation due to some stupid Cloudflare captcha checks. No, on Firefox, however many times I click that checkbox, I can't go through the verification, just to read some static content. Not even if I disable adblock and tracking protection.
I don't even see a checkbox at all on Chrome or Edge.
Cloudflare captchas are an excellent point.
Sure, technically nobody is excluded: Just solve the captcha! Fraud heuristics are only reasonable, right?
But it's all fun only as long as your situation occurs within the 90th or 95th percentile of all data labeled "good customer". Good luck if you're out side of that...
But thats not Chrome's fault.
I mostly use Chrome on Linux (fully Google distributed, closed source Chrome...so not Chromium) and I see those cloudflare captchas at a much higher rate than I do when using Windows or macOS.
This is also my experience. But to be fair I have a heavily modified privacy-centric Firefox, and I disabled some features in the config, and I disable js and large images and of course tracking/ads by default, and I delete most cookies on browser close, and I run Wayland on Linux so... any breakage is probably on me.
I almost always find that when sites do not work with Firefox (also Wayland on Linux) it works with Firefox (on the same machine) without the same plugins and settings.
Enabling JS is not enough, so I think its liked to privacy plugins, or running inside a container.
the cynic would say if you can't be tracked, you can't be monetized. unfortunately, being successfully un-de-anonymizable means you can't be distinguished from a bot.