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

WebReflection left a comment (whatwg/dom#736)

> If there's no path forward for improving the HTML parser situation maybe it makes sense for the web to push for an XHTML future once again.

I'd welcome that but right now HTML5 and XHTML are not fully interoperable (last time I've checked) so that would be a new world of potential incompatibilities between browsers, SSR and whatnot.

> it's possible for groups to break due to marker pairs being separated in the tree

not in my prototype ... those markers fail fast in that scenario so if you break the contract the fragment is broken, as easy as that. At the parsing level, if those markers are messed up no group exists ... still KISS and working with all primitives we have.

> That's going to impact users

not really ... it will impact bad code and libraries but those already negatively affect users ... I mean, some library still use `innerHTML` instead of preserving nodes identities, this is not a Web platform concern as long as specs are clear.

> will also need to be addressed in the DOM spec

true that, but the contract is very simple: https://github.com/WebReflection/group-nodes/blob/main/src/lib/utils.js#L74-L88

I would still welcome a `<fragment>` element but that's why I've asked for @rniwa consensus (or others) because I knew before proposing the prototype that would've been welcomed.

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

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