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

DeepDoge left a comment (whatwg/dom#736)

I really don't wanna create conflict but I really don't like the idea of:
> does not affect childNodes or children as it's meant to be transparent (differently from SD)

Transparent from query selectors? Yes! - _I mean naturally, since it's not an `Element` type._
Transparent from in `childNodes`? No, because it's a `ChildNode` in the DOM.
Filtered from `children`? Yes, because it's not an `Element` type.
Transparent in `children`, meaning `children` of fragment appear as if they are fragment's parent's `children`? No!

I don't think this needs to be over complicated, a basic container `ParentNode & ChildNode` with normal DOM hierarchy, and just transparent to query selectors, since it's not an `Element`. I don't think hacking with DOM hierarchy is good for JS.

---

Maybe it's already like this? and I miss understood what you meant there?

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

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