- From: Mason Freed <notifications@github.com>
- Date: Mon, 30 Oct 2023 14:32:00 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 30 October 2023 21:32:06 UTC
> And also, in the event the custom element creation was not parser-driven you'd have the exact same issue, but no solution, as you don't know when the `append()` calls will stop. So it's better to solve for that and then the parser case works too. Coming back to this - I wonder if you could provide an example of how you'd "solve for that" here? Maybe using the two concrete use cases provided in [this comment](https://github.com/WICG/webcomponents/issues/809#issuecomment-1755787377)? One is for the `<script>` element, and the other is about entry animations for a chunk of DOM. (Note that neither are custom elements, nor have imperative `append` equivalents, per-se.) -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/809#issuecomment-1786080425 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/809/1786080425@github.com>
Received on Monday, 30 October 2023 21:32:06 UTC