-
Notifications
You must be signed in to change notification settings - Fork 441
DOM lib: Add support for Trusted Types API #1246
New issue
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
Open
tosmolka
wants to merge
9
commits into
microsoft:main
Choose a base branch
from
tosmolka:trusted-types
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
c8f1dee
Add Trusted Types APIs
tosmolka 86656f9
Accept new baselines
tosmolka 6fd788f
Override Trusted Types Sinks
tosmolka 9832d8e
Accept new baselines
tosmolka 89141a7
Fix InnerHTML
tosmolka 678caa7
Merge branch 'main' of https://github.com/microsoft/TypeScript-DOM-li…
tosmolka b4156fb
Override setter types for Sink properties
tosmolka abe7b0a
Fix tests
tosmolka 517f616
Merge branch 'main' of https://github.com/microsoft/TypeScript-DOM-li…
tosmolka File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you give me some more insight into TrustedHTML nodes? Is it really this simple of an interface, or is there something "more" to them?
The reason I ask is that in a structural language like TypeScript, you could accidentally assign lots of stuff to
TrustedHTML
. Is there some internal runtime bit set, or is this really anything with atoJSON
and atoString
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TrustedHTML
is interesting, in that it's both an interface and also the name of a global object.So it's sort of like a class (you can do
value instanceof TrustedHTML
), but the main point of the API is that it can't be constructed without the Trusted Types API. Sort of like you have to dodocument.createElement("div")
instead ofnew HTMLDivElement()
.Each TrustedHTML instance is also associated with a specific string policy. So conceptually it might make sense to have something like
TrustedHTML<"dompurify">
. I don't know if it makes sense to include that in TypeScript, though. The"dompurify"
policy in that case is something that would be enforced by CSP for e.g.innerHTML
assignment, which seems a bit outside the scope of type checking.https://developer.mozilla.org/en-US/docs/Web/API/TrustedHTML#methods
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe consider emitting a class with a
private
constructor instead of an interface with only these very-widespread-methods (and the static pseudo-constructor)? That'd be allowable ininstanceof
and a private member should enable nominal checking (and thus forbid structural matches).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How would that interact with something like DefinitelyTyped/DefinitelyTyped#60417 ?
Element classes like
HTMLDivElement
are declared using the sameinterface
+var
pattern as this PR. Is there a particular reason to diverge from that entirely?For what it's worth,
new HTMLDivElement()
also doesn't error in TypeScript today.