- From: Robbie Speed <notifications@github.com>
- Date: Tue, 06 May 2025 16:20:29 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 6 May 2025 23:20:33 UTC
robbiespeed left a comment (whatwg/dom#736) @rniwa can you be more specific about what kinds of changes to parser behaviour is problematic? Template is a wildly different scenario, since it's children are placed into a `DocumentFragment` rather than as children of the element in the DOM tree (I see how that could've possibly lead to XSS with nonsupporting implementations). What's being proposed is something that from a parsing/DOM tree perspective behaves nearly identically to a regular element, with the difference being it may be placed in any parent element so long as it's children (or grand-children in a nested fragment case) are valid content of the fragments parent. The major change is with how the element behaves with CSS. From a backwards compatibility scenario it would end up a `HTMLUnknownElement` without the special transparent CSS behaviour or placement rules (would be moved outside a table for example). That seems pretty low risk. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/736#issuecomment-2856462428 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/736/2856462428@github.com>
Received on Tuesday, 6 May 2025 23:20:33 UTC