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

WebReflection left a comment (whatwg/dom#736)

I think we are overthinking this idea/proposal (me included) **but** it requires a lot of DOM prototype patching from userland ... which is not too bad, when it comes to polyfills, but imagine two projects land two different versions of that polyfill and you can see how that "*just polyfill it in userland*" solution is not really compelling ... that plus the fact tools need to have guidance around these things so that special comments won't be removed from minifiers or other processing.

After a lot of prototyping around this idea I think the ultimate goal would be to have `<!--<>-->` and `<!--</>-->` as special comments, but that comment could also be `<!--<GroupNodes>-->` and `<!--</GroupNodes>-->`.

The "*fragment*" would be represented by the starting comment where, if live, operates directly on that live range of nodes (start to end comments) while if not live, operates to its own private fragment.

A *WeakMap* can always return the handling reference out of that first node and thr tricky part is that no Range or other DOM manipulation should ever be able to break that contract where the start comment has no end comment out of that manipulated range.

the `isConnected` dance is delegated to the start comment node and all operations are delegated to the internal fragment, until the point it's not live, or to whatever parentNode the live content has.

I think this would make both native code and possible polyfills easy enough to reason about and implement so that basically this new node is just a comment by all means, but it implements a variant of ParentNode interface which delegates to the actual parent or its internal fragment (until live) all the things.

Like a fragment, it won't have `remove()` or other things in place except for that start node, where a `remove()` call will actually place back all nodes up to the *end* one in the internal fragment.

Again, happy to provide a concrete example of this idea but it's honestly the easiest I could think about to move this forward, yet the guard around not breaking those start/end comments boundaries via ranges remain the main, if not the only, issue to tackle at the Range level, the rest feels trivial to do.

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

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