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

Is there agreement in the HTML-spec community that no new injection sinks will be added? #399

Closed
mbrodesser-Igalia opened this issue Jan 15, 2024 · 5 comments

Comments

@mbrodesser-Igalia
Copy link
Collaborator

If so one, one could rely on TT staying trustworthy.

CC @mozfreddyb

@mozfreddyb
Copy link
Collaborator

I don't think it's necessarily "forbidden" to add new injection sinks and I don't think that's even necessary.

My assumption is that TT will need continued maintenance and care to make sure that it's kept in alignment with the web platform at large.
Secondly, I think there's a hope that with two aligned implementations, TT could be properly upstreamed into existing specs, which should make maintenance easier.

@lukewarlow
Copy link
Member

New DOM Sinks are definitely being added still, see #403

@mbrodesser-Igalia
Copy link
Collaborator Author

I don't think it's necessarily "forbidden" to add new injection sinks and I don't think that's even necessary.

My assumption is that TT will need continued maintenance and care to make sure that it's kept in alignment with the web platform at large. Secondly, I think there's a hope that with two aligned implementations, TT could be properly upstreamed into existing specs, which should make maintenance easier.

Agree. Then, ideally, the spec extension process should require trusted types for such new sinks. Is that process defined somewhere?

@lukewarlow
Copy link
Member

Hopefully once this is ready to go specs like HTML can make use of HTMLString directly and it can be more formal rather than this spec having to monkey patch each place. But it would still be good to ensure this sort of thing happens.

@mbrodesser-Igalia
Copy link
Collaborator Author

Closing this ticket since the original question was answered and the spec extension process will be covered by #385, see #385 (comment).

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

No branches or pull requests

3 participants