- From: Steve Orvell <notifications@github.com>
- Date: Wed, 16 Apr 2025 10:59:53 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 16 April 2025 17:59:57 UTC
sorvell left a comment (whatwg/dom#736) > Making this not a Node would make this proposal very similar to DOM parts. Yeah, I think this is the part that is throwing me, but I totally acknowledge that there's a practical benefit and my concerns may be pedantic. Similar virtual grouping primitives like `Range` and `<slot>` do not use "children" or "childNodes" to describe their virtual contents. Personally I find its usage here a little confusing, but I don't yet see any obvious practical concern. Pedantically, I know it's equivalent to iterate via `this.childNodes.forEach` or `while (start = start.nextSibling)`, but in `NodeGroup` we need `if (start === end) break;`. Again, I am not saying it's necessarily problematic. @rniwa does it violate any implementation constraint that a Node could be in more than one list of `childNodes`? -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/736#issuecomment-2810314403 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/736/2810314403@github.com>
Received on Wednesday, 16 April 2025 17:59:57 UTC