[go: nahoru, domu]

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

Fix type issue between get tt compliant string and validate string in context #497

Closed
wants to merge 1 commit into from

Conversation

lukewarlow
Copy link
Member
@lukewarlow lukewarlow commented Apr 4, 2024

Get TT compliant string now takes any value, rather than just string or a TT. It then correctly stringifies this value.

Fixes #488


Preview | Diff

… context

Get TT compliant string now takes any value, rather than just string or a TT. It then correctly stringifies this value.

Fixes w3c#488
@@ -1022,19 +1022,21 @@ This algorithm will return a string that can be used with an
It will ensure that the Trusted Type [=enforcement=] rules were respected.

Given a {{TrustedType}} type (|expectedType|), a [=realm/global object=] (|global|),
{{TrustedType}} or a string (|input|), a string (|sink|) and a string (|sinkGroup|), run these steps:
an [=ECMAScript language value=] (|input|), a string (|sink|) and a string (|sinkGroup|), run these 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.

If this now takes an ECMAScript language value which is what it's passed from the validate algorithm which gets it from WebIDL, does that "just work" for all the other uses of this algorithm? Or does it as I suspect break those call sites?

@lukewarlow lukewarlow requested a review from annevk April 4, 2024 13:15
@lukewarlow lukewarlow marked this pull request as ready for review April 4, 2024 13:15
@lukewarlow lukewarlow marked this pull request as draft April 4, 2024 14:42
@lukewarlow
Copy link
Member Author

Going to go ahead and close this because we're going ahead with removing the extended attribute.

@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
1 participant