Re: [WICG/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)

mangelozzi left a comment (WICG/webcomponents#551)

> [@frank-topel-dbi](https://github.com/frank-topel-dbi) fair concerns and questions but I see it like a `<no-script>` element or something that doesn't affect CSS or flexbox/grids just like `<script>` wouldn't too (or a comment) ... it can be still part of `children`, actually I think that would be expected ... does this simplify or drop some headache?

More expcetions  and changes that deviate from standard behaviour equals more complexity. When iterating nodes/children you need more exception logic to handle all these weird sort of edge cases. A callback (e.g. `closedTagParsed` (or choose your more appropiate name here) is a more cannonical way considering the current API.



-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/551#issuecomment-2660629719
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/551/2660629719@github.com>