otherdaniel / sanitizer Goto Github PK

Excuse my ignorance, does this proposal extend WICG/purification somehow?

Providing only way to sanitize attribute value using URL format might not be enough for some people, and I don't see (sorry if there is, just looked this quick) any way to sanitize attribute value except URL.

For example, Script Gadgets shows that sometimes, XSS could occur from id attribute (which is usually safe) with the help of frameworks.

For each website to block id attribute as a whole seems like a fragile approach. We should probably provide a way for people to declare custom sanitizer function for attribute value, or a way to list allowed attribute values at least.

Currently, triggering any HTML parser using DOM API makes Trusted Types angry, and Trusted Types requires sites to parse TrustedHTML.

Will saneStringFrom have same thing? Or will it never cause TT violation?

CC: @koto