You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although setting the meta http-equiv="origin-trial" content="<MYTOKEN>" does succeed in turning on the JSPI flag in the page...
...If I attempt to load WASM that requires JSPI in the ServiceWorker my page registers, I get the familiar WebAssembly.Function is not a constructor error (as though the JSPI flag wasn't enabled).
Is there something additional that needs to be done during SW registration to inform that side that JSPI is indeed supposed to be enabled?
The text was updated successfully, but these errors were encountered:
Although setting the
meta http-equiv="origin-trial" content="<MYTOKEN>"
does succeed in turning on the JSPI flag in the page......If I attempt to load WASM that requires JSPI in the ServiceWorker my page registers, I get the familiar
WebAssembly.Function is not a constructor
error (as though the JSPI flag wasn't enabled).Is there something additional that needs to be done during SW registration to inform that side that JSPI is indeed supposed to be enabled?
The text was updated successfully, but these errors were encountered: