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

@rniwa @mfreed7 waiting for the `template` end tag before updating the shadow tree is not a problem for Firefox. I don't think any of us is really convinced about the cost-benefit tradeoff however. Especially ending up with so many parser modes seems rather bad: script/noscript, fragment/no-fragment, shadow/no-shadow.

(As for what the copy-and-paste sanitizer should do, I hope we can standardize that as part of https://github.com/WICG/sanitizer-api. Looking at [a simple example](https://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A...x%3Ctest%20test%3Etest%3C%2Ftest%3E%3Cspan%20test%3Espan%3C%2Fspan%3Ex%3Cdiv%20contenteditable%3Eyy%3C%2Fdiv%3E) it does seem that Firefox is much more conservative there.)

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