I think part of the reason nobody tests for it anymore is just because web standards have largely gotten so good. I don't often test in FireFox these days myself largely in part because it just hasn't been a problem in years.

I'm old enough to remember the days when every change I made I had to roll through multiple versions of IE all the way back to 6, and different things would be broken in different versions.

It makes me shudder to remember when we had to include some outlandish workarounds just to make shadows work on IE6, not to mention custom web fonts.

Remember the Line25 "realistic shadows" pack??

(I cringe when I look at some of the emails I had with them back when I was 11, though...)

Transparent PNGs using CSS filter:progid:DXImageTransform.Microsoft.AlphaImageLoader is my shudder. Flat design would have made life so much easier back then.

The ghost of sIFR looms large in the memories of some.

Counterpoint: I use Firefox with every privacy setting maximized and several extensions installed, and I can't remember the last time I had an issue with something posted here. This game works fine for me as well.

The only apps that are noticeably worse in Firefox for me are Google Docs and Google Meet.

I use Google Docs and Google Meet (calling, webcam, screensharing) and it's perfectly fine on Firefox Linux. What do you mean?

I honestly do not know a single site that is broken with Firefox. What breaks sites is my strict DNS filtering setup, not the browser I use.

I feel first we need to validate the original premise that there's something wrong with this game in Firefox.

I'm running Firefox, with containers enabled, with ublock origins (and as such "somewhat privacy conscious over and above the defaults"), and this works fine for me.

There could be any number of things that cause an individual issue, which may or may not be related to Firefox itself :-/

Indeed, I have strict mode enabled, uBlock Origin, containers, and the game works completely fine.

Resist Fingerprinting was enabled. I updated my comment to note that.

BTW, Resist Fingerprinting's main impact (for me) has been to increase triggering of "Click and Hold to prove you are not a bot" on sites relying on fingerprinting as an anti-bot measure (Drupal, Walmart, Kickstarter). On some of those, the developer doesn't even realise that measure can trigger, and it triggers in a background XHR (Kickstarter does this sometimes).

This is still better than some other sites like Lowes and Fedex where the entire site (Lowes) or backend API (Fedex package tracking) simply errors due to an Akamai block without any option to prove yourself. For those, you pretty much just have to use another Firefox profile with fingerprinting allowed (or another website).