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

> @rniwa, as I [mentioned](https://github.com/whatwg/html/pull/5465#issuecomment-1264146315) on the PR, I'm excited to hear you're prototyping a streaming version of this feature! Interesting performance results - but I guess not too surprising. I've [said](https://github.com/whatwg/dom/issues/831#issuecomment-1215603768) that the overhead of moving the nodes around at the closing `</template>` tag wasn't too high, so it's good to see you've confirmed that on an independent prototype.

Right, I wanted to do independent analyze the perf in WebKit.

> The biggest benefit of this approach is that it allows streaming, which is a highly developer-requested feature (generally, but also for DSD). [Your primary objection to streaming before](https://github.com/whatwg/dom/issues/510#issuecomment-370980398) was the complexity of modifying the parser to do streaming DSD - what did you find after prototyping it? How complex was the patch to support streaming, vs the one that attaches at the closing tag?

Our prior objection was more based on rendering & exposing half-baked shadow DOM to scripts. There was also a concern that exposing half-baked shadow tree can lead to new security bugs in the parser. However, a lot of people seem to want streaming for this feature so maybe we should do it despite of the risk of complications.


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

Message ID: <whatwg/dom/issues/831/1267310676@github.com>