4 ms·

I get the same thing, but I've been ignoring it because that can be a rabbit hole. I've seen lots of advice just to get something small published if you want to

• lioeters 4y ago
  I was just reading about SharedArrayBuffer recently, specifically about supporting Firefox. Lemme see if I can find it in my notes.. Ah yes, it was about ffmpeg.wasm which requires this feature. Apparently this security restriction is coming to Chrome also. Does not work in Firefox 79+ because SharedArrayBuffer is undefined #106 - https://github.com/ffmpegwasm/ffmpeg.wasm/issues/106 https://github.com/ffmpegwasm/ffmpeg.wasm/issues/106 --- The solution is to add cross-origin headers. > As a baseline requirement, your document needs to be in a secure context. https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts https://developer.mozilla.org/en-US/docs/Web/Security/Secure... > For top-level documents, two headers need to be set to cross-origin isolate your site: Cross-Origin-Opener-Policy: same-origin Cross-Origin-Embedder-Policy: require-corp SharedArrayBuffer: Security requirements - https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer#security_requirements https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...