WebAssembly.Memory causes issues with content security policy
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Safari throws an error when loading with a content security policy that doesn't include 'unsafe-eval' in script-src. It seems to be the odd man out. I don't know what can be done to work around it.
https://github.com/WebAssembly/content-security-policy/blob/master/proposals/CSP.md
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Safari error while loading sql.js under a script-src policy without 'unsafe-eval'. Read the linked WebAssembly CSP proposal and compare its guidance with the reported WebAssembly.Memory behavior. Done means identifying a viable workaround or clearly documenting that Safari cannot support this configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, wasm
- Domain
- security, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100