Conversation
Provide background on CSP threat model and use cases
Pull in latest changes from WebAssembly/spec repo
Rename 'wasm-eval' to 'wasm-unsafe-eval' Fixes #15.
Remove reference to mimetype hardening
Always allow WebAssembly.validate()
Rework final table for clarity
Summarize API behavior and threats relative to CSP
At yesterday's WG meeting, we decided to make a new release, now switching to the Evergreen model. For administrative and technical reasons having to do with W3C procedure, we decided to bump the release number to 2. From now on, the standard will iterate at version 2 from the W3C's official perspective. We use minor release numbers internally to distinguish different iterations. (@ericprud, I hope I understood correctly that the Bikeshed "level" also needed to be bumped to 2.)
Redundant: already covered in js-api
Merge from upstream wasm 3.0
Not needed in web-api spec.
tlively
reviewed
Jun 23, 2026
tlively
left a comment
tlively
left a comment
Member
There was a problem hiding this comment.
Are there expected to be any tests here?
Member
There was a problem hiding this comment.
Are the deletions here expected? It seems it would be better to edit the "Security and Privacy Considerations" section rather than remove it.
rossberg
reviewed
Jun 23, 2026
| [](https://github.com/WebAssembly/spec/actions/workflows/ci-spec.yml) | ||
| [](https://github.com/WebAssembly/spec/actions/workflows/ci-interpreter.yml) | ||
|
|
||
| # Content Security Policy Proposal for WebAssembly |
Member
There was a problem hiding this comment.
You'll want to undo the changes to the README.
Removed the Content Security Policy proposal section from the README.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This (should) reflect changes needed to incorporate phase 4 csp.
This should probably NOT just be merged, as the change seems to include notes that might not normally be part of the spec.