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

WebReflection left a comment (whatwg/dom#736)

> Right now, comment nodes are used for similar behavior which is a hack, and it can break the framework when DOM is mutated without the framework, which is absurd.

confirmed, but also that hack works in all scenarios around `<LI>`, `<TR>` and all other elements that would **not** support a different *parentNode* from the one accepted by current standard ... meaning, if this `<group>` idea won't allow grouping `<LI>` or `<TR>` in it without breaking the layout/parser, we're back to just another element-like container ... this is kinda extremely important to keep in mind or use cases around the desired of a "*transparent and persistent fragment*" will be all gone.

The list of elements that would need an amend is "*relatively short*" if we exclude those within the *head*, hence not meant to pollute the layout/rendering/parsing goal: https://gist.github.com/WebReflection/266897efa84a82534f7ffe17aadaba3b

Still, while comments work around all these, I can see the effort to make this `<group>` idea nearly as high as the *persistent fragment* one and, if it cannot solve use cases comments solve already, I can see low adoption and still the need for the specific framework to deal with those nodes.

Thanks for pointing that out though, it's OK to have "*something*" instead, but if that something ends up requiring a lot of work without solving the reason people are using open/close or close only comments, bound to the nodes these represents, that effort would be rather spent elsewhere, imho.

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

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