Luke Warlow

# Trusted Types integration with DOM The DOM spec already contains partial integration with Trusted Types this was included in https://github.com/whatwg/dom/pull/1258 This PR updates the DOM functions related to attributes....

The change to `set an attribute value` breaks iframe.srcdoc property setting currently (it'll do a double check). It's possible that there's other reflection properties that have the same issue (script.src...

> This now seems to invoke TT even when we have specifications manipulate attributes, Should I add a verify flag to these other algorithms so they can't be accidentally invoked...

If others are happy with that idea I'm happy to look into updating this PR to match.

I've pushed up the change to "set an attribute", and to "set an existing attribute value". I'm looking into the setAttribute methods now. > Attr.value/.nodeValue/.textContent should do validation (if there...

cc @otherdaniel as he did the Chromium implementation

I'll take some more time to properly read through and respond but regarding how correct the "is changed by API" bit is. Chromium used to (and right now WebKit still...

Following up on this I've opened a draft PR on Trusted Types which tries to advaced the script protection. I've moved to a new model after discussions with Anne and...

Making draft as I've found a number of inconsistencies across browsers and I'm trying to work out which browser is actually correct

Superseded by https://github.com/web-platform-tests/wpt/pull/49461