3 ms·
Admittedly we have not tested on firefox as much, but I suspect that is happening is that we have a race condition in waiting for the 30+MB package of wasm and
by freeciv21 5y ago
Admittedly we have not tested on firefox as much, but I suspect that is happening is that we have a race condition in waiting for the 30+MB package of wasm and data files to load.
- mikea1 5y agoThis is impressive and shows a lot of dedication! How are you hosting the site and assets?
- freeciv21 5y agoHetzner, with Cloudflare to do the CDN for such large game assets.
- fouc 5y agoI generally think it'd be wise to develop for either Safari or Firefox first. Then fix for Chrome after. i.e. develop for the underdog(s) first.
- pmarreck 5y agosame issue in FF I think. "Couldn't start server"... and it is a pretty quick timeout, like 2 seconds