setInterval(code) - update with TrustedScript #41403
Open
+126
−105
Conversation
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
github-actions
bot
added
Content:WebAPI
32 tasks
|
Preview URLs (comment last updated: 2025-10-12 23:52:31) |
hamishwillee
force-pushed
the
tt_window_setinterval
branch
from
7b8d70f to
47af7b8
Compare
hamishwillee
commented
Oct 12, 2025
|
|
||
| ## Examples | ||
|
|
||
| ### Example 1: Basic syntax |
There was a problem hiding this comment.
Note, I didn't add a trusted type example because to my mind it isn't the main use case with this. I can add one if you think it useful.
hamishwillee
commented
Oct 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 updates the TrustedScript documentation for
Window/setInterval()to include information about using it with trusted types.A lot of this was to update the doc to current template - such as moving Usage notes under description and so on.
I also thought it worthwhile to purge mention of getting things to work with IE, and focus on how you get the "this" right rather than not being able to get it right on legacy JavaScript.
The security considerations mostly mention CSP since generally the
codeoption is disabled by default.I will look at
setTimeout()after this, since the changes would be mostly the same.Project tracking in #37518