Do you mind sending me an example page of a broken game so I can take a closer look? It can be draft or restricted. Thanks
Viewing post in Cross Origin Policies for Webassembly
An example game would be SNAKE SNAKE SNAKE.
In Chrome it will work just fine, in Firefox you will get the following error: Uncaught ReferenceError: SharedArrayBuffer is not defined
This is a LÖVE game that has been ported with Love.js.
Hmm no it doesn't run on Firefox for me. I still get the error "Uncaught ReferenceError: SharedArrayBuffer is not defined". Does it work for you?
Edit: I should probably check if the game works on a website if it has those headers. I will test that out.
Edit 2: I hosted it on my website with the following in my .htaccess and it works
Header set Cross-Origin-Opener-Policy: same-origin
Header set Cross-Origin-Embedder-Policy: require-corp
Thanks for testing. I was only testing by loading the iframe contents directly, but it looks like the entire chain of embedding pages will need have their headers updated.
I’ve identified some breaking issues with these headers for existing games though, so I’ve decided to turn off these headers for now.
It looks like we’ll probably have run two separate CDN configurations at the same time to ensure maximum compatibility. Our backend storage does not let use set headers per object, so these headers will have to be globally injected at the CDN. So I’ll likely have a Legacy mode and a New mode for when you choose how your HTML5 games are delivered.
Just wanted to pop in and say I am having the same exact issue running a LOVE2D game in Firefox that was transpiled via Love.js.
EDIT: In case it's useful, here is the game where I am having the same issue (loads fine in Chrome and Chromium browsers but not Firefox/Safari) - https://elennick.itch.io/httpselennickitchiosuper-moonshot-adventure