This is a user help forum if there is issue you need to send it by bugzilla for the devs team to look at.

... you need to send it by bugzilla for the devs team to look at.

The general issues tracker Bugzilla is not for support purposes as ideally one needs to have the causes and have a reproducible case before filling a bug, otherwise they may just tell the bug filer to get support here first.

markwarner22 said

... you need to send it by bugzilla for the devs team to look at.

The general issues tracker Bugzilla is not for support purposes as ideally one needs to have the causes and have a reproducible case before filling a bug, otherwise they may just tell the bug filer to get support here first.

I think it's more like a removal of a designed limitation requirement instead of a bug report. I am not sure where to file it.

Sorry, after some tests, I believe the WASM performance is no longer better than the latest Chrome. There is a significant 10% percent performance difference compare to Chrome. For instance: Quake, Chrome scores 32 fps meanwhile Firefox only achieves 28 fps. It used to be Firefox is faster than Chrome we've tested before.

That’s a solid point. Firefox’s IndexedDB value limit (~2MB per entry) has been a known constraint for a while. It’s unfortunate because their WASM performance is excellent, but the IDB limit makes it harder to run asset-heavy games. Chunking data can work, but it complicates the logic. I ran into the same issue while testing a game on my side project, Gratis Solitär — and had to restructure how I handle saves. Would definitely be nice to see Mozilla loosen that limit in future versions.