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.

Sign up for GitHub

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

Jump to bottom

Is the [[ScriptURL]] slot needed? #401

Closed
lukewarlow opened this issue Jan 15, 2024 · 1 comment · Fixed by #418
Closed

Is the [[ScriptURL]] slot needed? #401

lukewarlow opened this issue Jan 15, 2024 · 1 comment · Fixed by #418
Labels
proposed-removal Issues concerning potential removal of functionality from the API

Comments

@lukewarlow
Copy link
Member

https://w3c.github.io/trusted-types/dist/spec/#slots-with-trusted-values - say

Figure out if we can drop [[ScriptURL]] slot after IDL + DOM changes.

So we need to figure out if it can indeed be dropped as a result of any other changes that have been made in this spec (or if there's work needed to achieve it?).
@koto koto added the proposed-removal Issues concerning potential removal of functionality from the API label Jan 18, 2024
@koto
Copy link
Member

koto commented Jan 22, 2024

I'm working on the DOM integration draft and have reviewed the algorithms. [[ScriptURL]] extended attribute will not be needed in the end, I'll remove it together with the DOM changes.

koto added a commit to koto/trusted-types that referenced this issue Jan 23, 2024
@koto
Rewrote DOM integration, adding an expliting entry point algorithm to
4d2c854 
call from DOM.

whatwg/dom#789
Closes w3c#401.
@koto koto mentioned this issue Jan 23, 2024
Merged
koto added a commit to koto/trusted-types that referenced this issue Jan 23, 2024
@koto
Rewrote DOM integration, adding an expliting entry point algorithm to
7820b21 
call from DOM.

whatwg/dom#789
Closes w3c#401.
koto added a commit to koto/trusted-types that referenced this issue Jan 23, 2024
@koto
Rewrote DOM integration, adding an expliting entry point algorithm to
6702593 
call from DOM.

whatwg/dom#789
Closes w3c#401.
koto added a commit to koto/trusted-types that referenced this issue Jan 23, 2024
@koto
Rewrote DOM integration, adding an expliting entry point algorithm to
af81fe0 
call from DOM.

whatwg/dom#789
Closes w3c#401.
koto added a commit to koto/trusted-types that referenced this issue Jan 23, 2024
@koto
Rewrote DOM integration, adding an expliting entry point algorithm to
88d6c40 
call from DOM.

whatwg/dom#789
Closes w3c#401.
@koto koto closed this as completed in #418 Feb 1, 2024
koto added a commit that referenced this issue Feb 1, 2024
@koto @lukewarlow
Rewrote DOM integration (#418)
d5d9ee9 
Rewrote DOM integration, adding an expliting entry point algorithm to
call from DOM.

whatwg/dom#789
Closes #401.

Co-authored-by: Luke Warlow <lwarlow@igalia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
proposed-removal Issues concerning potential removal of functionality from the API
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Rewrote DOM integration koto/trusted-types
2 participants
@koto @lukewarlow