Re: [WICG/webcomponents] Need a callback for when children changed or parser finished parsing children (#809)

@WebReflection you mention the two parser cases, but you fail to mention the other way an element has to work: through imperative creation and insertion. And for parity with builtin elements that ought to work in whichever way web developers want to do things. It shouldn't impose inserting children before insertion into the document, for instance. Just think about all the ways you can end up with a `<select>` element and descendants in the tree. Whichever way you go about it, it'll work. That's the bar.

(Also, you posted 4 comments in a 2-hour period. Please amend existing comments instead. There's a lot of people watching this repository. Be mindful of their time and attention.)

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

Message ID: <WICG/webcomponents/issues/809/1463846026@github.com>