Skip to content
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

Make sink an argument to get tt compliant attribute value #493

Closed
wants to merge 1 commit into from

Conversation

lukewarlow
Copy link
Member

@lukewarlow lukewarlow commented Mar 28, 2024

Partly address #492


Preview | Diff

@lukewarlow lukewarlow requested a review from koto March 28, 2024 10:50
@@ -1081,24 +1081,23 @@ Given an {{HTMLScriptElement}} (|script|), this algorithm performs the following
If the algorithm threw an error, rethrow the error.

## Get Trusted Types-compliant attribute value ## {#validate-attribute-mutation}
To <dfn abstract-op export>get Trusted Types-compliant attribute value</dfn> on {{Attr}} |attribute| with {{Element}} |element| and {{TrustedType}} or a string |newValue|, perform the following steps:
To <dfn abstract-op export>get Trusted Types-compliant attribute value</dfn> on {{Attr}} |attribute| with {{Element}} |element|, {{TrustedType}} or a string |newValue|, and string |sink|, perform the following steps:
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of the sink being HTMLIFrameElement srcdoc it will be something like Element setAttribute or Attr value this matches Chrome's behaviour.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to double check which is correct though does Chrome's impl need updating or is the spec currently just wrong in this case?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Though this change does mean the DOM integration needs to wire through the sinks from the IDL all the way down to the call out to this spec?

@lukewarlow
Copy link
Member Author

Matching commit to the DOM spec PR whatwg/dom@6565089

@lukewarlow lukewarlow closed this Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant