-
Notifications
You must be signed in to change notification settings - Fork 74
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
Add tests for setAttribute
/setAttributeNS
's sink names
#570
Comments
moz-wptsync-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this issue
Jan 1, 2025
…lue". "get Trusted Types-compliant attribute value" is called from `setAttribute*`, for links see the test. `setAttribute` and `setAttributeNS` presumably take the same code-paths, so only testing `setAttributeNS` here. For event handlers only one test is added, because other event handlers presumably take the same code-paths. Fixes w3c/trusted-types#570. Differential Revision: https://phabricator.services.mozilla.com/D233035 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1907849 gecko-commit: 42f2f0e18f47e959d64f305cac2c313f34296ce8 gecko-reviewers: smaug
moz-v2v-gh
pushed a commit
to mozilla/gecko-dev
that referenced
this issue
Jan 1, 2025
… attribute value". r=smaug "get Trusted Types-compliant attribute value" is called from `setAttribute*`, for links see the test. `setAttribute` and `setAttributeNS` presumably take the same code-paths, so only testing `setAttributeNS` here. For event handlers only one test is added, because other event handlers presumably take the same code-paths. Fixes w3c/trusted-types#570. Differential Revision: https://phabricator.services.mozilla.com/D233035
moz-wptsync-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this issue
Jan 2, 2025
…lue". "get Trusted Types-compliant attribute value" is called from `setAttribute*`, for links see the test. `setAttribute` and `setAttributeNS` presumably take the same code-paths, so only testing `setAttributeNS` here. For event handlers only one test is added, because other event handlers presumably take the same code-paths. Fixes w3c/trusted-types#570. Differential Revision: https://phabricator.services.mozilla.com/D233035 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1907849 gecko-commit: 42f2f0e18f47e959d64f305cac2c313f34296ce8 gecko-reviewers: smaug
i3roly
pushed a commit
to i3roly/firefox-dynasty
that referenced
this issue
Jan 2, 2025
… attribute value". r=smaug "get Trusted Types-compliant attribute value" is called from `setAttribute*`, for links see the test. `setAttribute` and `setAttributeNS` presumably take the same code-paths, so only testing `setAttributeNS` here. For event handlers only one test is added, because other event handlers presumably take the same code-paths. Fixes w3c/trusted-types#570. Differential Revision: https://phabricator.services.mozilla.com/D233035
This is fixed by web-platform-tests/wpt@0da103c but my github account does not have the proper permission to close the issue. cc @lukewarlow @koto |
sadym-chromium
pushed a commit
to web-platform-tests/wpt
that referenced
this issue
Jan 14, 2025
…lue". "get Trusted Types-compliant attribute value" is called from `setAttribute*`, for links see the test. `setAttribute` and `setAttributeNS` presumably take the same code-paths, so only testing `setAttributeNS` here. For event handlers only one test is added, because other event handlers presumably take the same code-paths. Fixes w3c/trusted-types#570. Differential Revision: https://phabricator.services.mozilla.com/D233035 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1907849 gecko-commit: 42f2f0e18f47e959d64f305cac2c313f34296ce8 gecko-reviewers: smaug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Step 5 of https://w3c.github.io/trusted-types/dist/spec/#abstract-opdef-get-trusted-types-compliant-attribute-value receives the sink value obtained from https://w3c.github.io/trusted-types/dist/spec/#abstract-opdef-get-trusted-type-data-for-attribute.
CC @fred-wang
The text was updated successfully, but these errors were encountered: