-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Trusted types integration dom #6057
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
Trusted types integration dom #6057
Conversation
3b2562d to
be7bf5b
Compare
|
Your pull request has conflicts that need to be resolved before it can be reviewed and merged. Make sure to rebase your branch on top of the latest |
be7bf5b to
75accf6
Compare
75accf6 to
db339f5
Compare
|
Your pull request has conflicts that need to be resolved before it can be reviewed and merged. Make sure to rebase your branch on top of the latest |
db339f5 to
6ffd0c1
Compare
0e42cd9 to
97a6433
Compare
97a6433 to
bc7ee2e
Compare
Lubrsi
left a comment
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.
Good work, here's a handful of issues I found
f548e86 to
658f63f
Compare
|
Your pull request has conflicts that need to be resolved before it can be reviewed and merged. Make sure to rebase your branch on top of the latest |
658f63f to
f340bbd
Compare
fa0ea61 to
a76bf66
Compare
This part of the spec is still under a PR in GitHub, but it should be safe to implement like it is.
This function was supposed to throw errors even before the TrustedTypes spec thanks to the CharacterData replaceData call but had a MUST. This changes this to ensure this function can throw an error
a76bf66 to
78de0e2
Compare
This should cover most of the integration with TrustedTypes and the DOM apis
In particular this is the work required to implement Section 4.2 of the TrustedTypes Spec.
It follows the MR of whatwg/dom#1268 as close as we can given it is not merged yet.
There is 2 special points we need to be aware of:
execCommandis ad-hoc since that standard was abandoned. There are some WPT test to cover them and my goal was to make the test pass and what made sense in my head.csp-violations.jsbut it means we won't see them in our official WPT score until we solve https://github.com/LadybirdBrowser/ladybird/blob/master/Libraries/LibWeb/WebSockets/WebSocket.cpp#L191. I gave it quick try with not much hope but it is clearly outside the scope of this MR.