- From: Shiba <notifications@github.com>
- Date: Thu, 24 Apr 2025 05:45:56 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 24 April 2025 12:46:00 UTC
DeepDoge left a comment (whatwg/dom#736) @WebReflection I was just saying, it wasn't a problem with all the things you listed. > 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. Also, I just seen it more of small change by introducing a new primitive like new attribute that makes the element transparent, which also might be useful for other use cases other than "fragments" as well. Instead of engineering something new. I never said it should be that in the whole page. From the start I was just saying that I don't like that `.parentNode` is giving the parent of the fragment that all. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/736#issuecomment-2827491184 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/736/2827491184@github.com>
Received on Thursday, 24 April 2025 12:46:00 UTC