♻️🐛 [Trusted Types] Make createExtensionScript Trusted Types compatible #2
Conversation
This file contains 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
eozmen410
reviewed
Jun 12, 2023
aaronshim
approved these changes
Jun 13, 2023
eozmen410
approved these changes
Jun 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 change updates AMP's createExtensionScript function to be Trusted Types compatible, partial fix to ampproject#37297. The function was directly setting the scriptElement.src to some variable url. This url is expected to fall under the cdn so we can restrict the host the url takes on to cdn.ampproject.org and return the url as being a TrustedScriptUrl.