Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

syscall/js: requires unsafe-eval with Content Security Policy #26748

Closed
xudongzheng opened this issue Aug 1, 2018 · 1 comment
Closed

syscall/js: requires unsafe-eval with Content Security Policy #26748

xudongzheng opened this issue Aug 1, 2018 · 1 comment
Labels
arch-wasm WebAssembly issues FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@xudongzheng
Copy link
Contributor

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.

@gopherbot
Copy link
Contributor

Change https://golang.org/cl/127296 mentions this issue: syscall/js: move callback helper code to misc/wasm to avoid using eval()

@bradfitz bradfitz added NeedsFix The path to resolution is known, but the work has not been done. arch-wasm WebAssembly issues labels Aug 1, 2018
@bradfitz bradfitz added this to the Go1.11 milestone Aug 1, 2018
@golang golang locked and limited conversation to collaborators Aug 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly issues FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants