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

I'm concerned mostly about the migration path for existing codebases that
are based on writing content attributes. It's not just a simple replacement
from using element attributes to it's properties.

The attrs do not need to store custom type values, we might only make
setAttribute not stringify the 2nd argument (+it's namespaces version),
which could be picked up by change steps defined in HTML / csp.

I already noticed that attribute change steps in HTML return early (before
attr value is set) e.g. when csp blocks event handlers. Perhaps this logic
could be used in the se way. The only new part would then be just the
signature of setAttribute function.

On Thu, Nov 14, 2019, 15:49 Anne van Kesteren <notifications@github.com>
wrote:

> It makes more sense to me if types always go through IDL attributes and
> content attributes remain strings forever.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/whatwg/dom/issues/789?email_source=notifications&email_token=AAA7JKZEUXHIBD3HVFVVWM3QTVQQ3A5CNFSM4I74BDO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEECCSBY#issuecomment-553920775>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAA7JK2DGSDPD4LZAHTQLBLQTVQQ3ANCNFSM4I74BDOQ>
> .
>


-- 
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-554017840