Re: [whatwg/dom] Trusted Types integration (#789)

For example: one only creates the value once, and may use it in various sinks; so TT might only require to change the code that produces the value (say, a function that generates the URLs for dynamic script loads), and not all the places where this data ends up in the DOM. 

I can also imagine some situations where there is a difference in behavior between `setAttribute` and property setting, that might make transition from one to the other more difficult than a simple string replacement. All our existing integrations used both properties and attributes for various reasons [example: React](https://github.com/facebook/react/blob/master/packages/react-dom/src/client/DOMPropertyOperations.js). If TT are agnostic to whether you use content or IDL attributes, the migration must be strictly simpler, no?



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/789#issuecomment-554447629