We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm opening this issue to discuss whether and what parts of the trusted types spec should be upstreamed to the CSP spec.
We currently define extensions to the CSP spec in https://w3c.github.io/trusted-types/dist/spec/#integration-with-content-security-policy
While some of this would probably be fine to stay in trusted types, there is a section that monkey patches EnsureCSPDoesNotBlockStringCompilation https://w3c.github.io/trusted-types/dist/spec/#csp-eval
EnsureCSPDoesNotBlockStringCompilation
cc @bkardell
The text was updated successfully, but these errors were encountered:
Minutes of the discussion: https://github.com/w3c/webappsec/blob/main/meetings/2024/2024-03-20-minutes.md#trusted-types
Sorry, something went wrong.
No branches or pull requests
I'm opening this issue to discuss whether and what parts of the trusted types spec should be upstreamed to the CSP spec.
We currently define extensions to the CSP spec in https://w3c.github.io/trusted-types/dist/spec/#integration-with-content-security-policy
While some of this would probably be fine to stay in trusted types, there is a section that monkey patches
EnsureCSPDoesNotBlockStringCompilation
https://w3c.github.io/trusted-types/dist/spec/#csp-evalcc @bkardell
The text was updated successfully, but these errors were encountered: