Conversation
As noted in #426, the current "Does element match source list for type and source?" algorithm does not properly handle `strict-dynamic` checks for non-parser-inserted inline scripts. This patch adds a relevant step to the algorithm to match both browser behavior and our existing tests: https://wpt.fyi/results/content-security-policy/script-src/script-src-strict_dynamic_non_parser_inserted.html?label=experimental&label=master&aligned Fixes #426.
Member
Author
|
Would you mind taking a look at this, Antonio? All browsers are currently aligned on the behavior, and it's locked in with tests. |
Member
Author
|
Friendly ping, Antonio. :) |
antosart
approved these changes
Oct 29, 2025
Member
antosart
left a comment
antosart
left a comment
There was a problem hiding this comment.
Thanks and sorry for the delay, I missed this.
Lubrsi
added a commit
to Lubrsi/ladybird
that referenced
this pull request
Feb 10, 2026
This implements w3c/webappsec-csp#787 that fixed the linked spec issue.
Lubrsi
added a commit
to Lubrsi/ladybird
that referenced
this pull request
Feb 10, 2026
This implements w3c/webappsec-csp#787 that fixed the linked spec issue.
Lubrsi
added a commit
to Lubrsi/ladybird
that referenced
this pull request
Feb 10, 2026
This implements w3c/webappsec-csp#787 that fixed the linked spec issue.
Lubrsi
added a commit
to Lubrsi/ladybird
that referenced
this pull request
Feb 10, 2026
This implements w3c/webappsec-csp#787 that fixed the linked spec issue.
Lubrsi
added a commit
to Lubrsi/ladybird
that referenced
this pull request
Feb 13, 2026
This implements w3c/webappsec-csp#787 that fixed the linked spec issue.
shannonbooth
pushed a commit
to LadybirdBrowser/ladybird
that referenced
this pull request
Feb 19, 2026
This implements w3c/webappsec-csp#787 that fixed the linked spec issue.
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
2 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.
As noted in #426, the current "Does element match source list for type and source?" algorithm does not properly handle
strict-dynamicchecks for non-parser-inserted inline scripts. This patch adds a relevant step to the algorithm to match both browser behavior and our existing tests:https://wpt.fyi/results/content-security-policy/script-src/script-src-strict_dynamic_non_parser_inserted.html?label=experimental&label=master&aligned
Fixes #426.
Preview | Diff