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

FrameMuse left a comment (whatwg/dom#736)

> [@FrameMuse](https://github.com/FrameMuse) you are asking for something already solved in userland specs don't believe or understand is needed ... this is like a `<fragment>` element that doesn't exist for CSS or the tree resolution, something not easy to implement due legacy behavior.
> 
> I've written a polyfill for this already and that was years ago, nobody cared and no progress is happening ... I believe this won't ever be part of these HTML specs due legacy presence and effort to bypass all legacy assumptions about trees and whatnot ... yet I hear you, just here to assure you everything you are asking for has been asked for exactly the same for years and no progress or interest ever happened.
> 
> This is a "_ghost issue_" ... one of those kept opened for some reason but one of those that we'll see an outcome in 10 years, if ever 🤷

I understand your frustration, but it doesn't mean we should be yelling about it's impossibility of being accepted, let's just discuss things you already implemented here, so it's at least visible to others.

I think nobody has cared because VanilaJs is not so popular choice when we have lots of frameworks allowing a developer the least possible interaction with it.

I saw your code, it comes with additional friction like `valueOf`, which is ok for frameworks and it has several uncovered edge cases (maybe I tested wrong/old version of your code), which are important for me.

Could you add a TL;DR comment below with h1 heading, please? So everyone else coming here would see all the information needed and don't go in circles (I would appreciate as well).

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

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