Re: [whatwg/dom] Declarative Shadow DOM (#831)

@rniwa
> For example, you can't place `<shadow>` as a child of `<table>` because of the HTML parsing behavior. There are a few other odd behaviors in HTML which forbid `<shadow>` to appear as a child or a parent of certain elements. 

Not sure if it s good idea but what about adding shadow doms via attributes then aka `<tbody componentmode="open">`? 

IMHO shipping this feature _as proposed_ without an opt-in http-header/meta-tag means xss sanitizers (even if it is the fault of the sanitizer) may not be prepared and web authors would be backstabbed by a change of reality introduced by browser vendors. 

If - however - you have to **_explicitly_** opt-into the feature, the responsibility does not lie where the standard is being created, and that should be enough.

-- 
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/831#issuecomment-716178439