Re: [whatwg/dom] Proposal: a DocumentFragment whose nodes do not get removed once inserted (#736)

rniwa left a comment (whatwg/dom#736)

> I wanted to join the meeting, but it was too late for me eventually (as for Europe time, it was almost midnight), it would be awesome if another meeting is scheduled, so [@WebReflection](https://github.com/WebReflection) (the author of this proposal), others and I could join it on the convenient time.

Yeah, timing wasn't ideal for folks in Europe. Hope we can schedule another zoom call / google meet in more European friendly time slot.

> > Could people who are supportive of this proposal also review the [DOM parts proposal](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/DOM-Parts-Imperative.md) and let us know whether that proposal also address your use cases? If not, we'd really like to understand why. Since two proposals are quite similar in terms of their target use cases, we'd like to better understand how the semantic difference between the two affects usage in practice.
> 
> This is exactly what I was considering for some time already, I've come up with some good IMO examples for VanilaJS. So personally, I can state that beyond applications and avoiding Nodes patching for frameworks (rendering libraries), it definitely has its impact on how you approach certain complex cases such as: **Conditional Rendering**, **Dynamically Paged Lists**, **"tandem" grouping of elements** (e.g. `div` + `hr` group) and Encapsulation of nodes (ones can be managed in isolation while being added by another script).

So what is your conclusion? Does DOM part proposal also address your use cases? Or if not, why not?


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

Message ID: <whatwg/dom/issues/736/2756965291@github.com>