- From: Shiba <notifications@github.com>
- Date: Thu, 24 Apr 2025 03:17:04 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/dom/issues/736/2827085431@github.com>
DeepDoge left a comment (whatwg/dom#736) > * `<li>` ... these cannot be appended within an outer element > * `<head>` related children that could be grouped by feature-detection/UA sniffing (as ugly as that is, it's still very much used out there) > * `<td>` or `<tr>` cannot be appended without breaking tables > * `<option>` cannot be appended > * `<source>` or other strictly constrained by their parent (and vice-versa) that cannot be everywhere Btw, I just wanted to say `<li>`, `<option>`, `<title>`, and more are not effected. `<td>` `<tr>` also not effected in DOM. But HTML parsing throws the `div`(s) out of the `<table>`. Similar to how HTML parsing throws the nested `<form>`(s) out, but its totally fine and handled well when appended by JS. I already use `<div is="..." style="display: contents">` on elements to wrap reactive `ChildNodes` in the DOM, in my library, which I'm using in few projects already. Only down side for me was external CSS libraries might trip sometimes because the selectors in them don't expect something in between. And that's the only reason I'm interested in this. That's all I wanted to say. Just watching where this proposal goes. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/736#issuecomment-2827085431 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/736/2827085431@github.com>
Received on Thursday, 24 April 2025 10:17:08 UTC