syscall/js: requires unsafe-eval with Content Security Policy #26748
Labels
arch-wasm
WebAssembly issues
FrozenDueToAge
NeedsFix
The path to resolution is known, but the work has not been done.
Milestone
Currently running go1.11beta2. When using the compiled .wasm with misc/wasm/wasm_exec.js, we get an error message if the site prohibits eval() via the Content-Security-Policy header. This can be resolved by moving the callback helper code src/syscall/js/callback.go to misc/wasm/wasm_exec.js.
The text was updated successfully, but these errors were encountered: