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

> Well, I think the problem is that an end tag notification doesn't cover all cases. If you cannot handle dynamic insertion and mutation of those insertions, how can you claim to be a proper element?

I agree - dynamic content needs to be handled as well. There are tools for that, e.g. `MutationObserver`. However, there's no tool to notify a component that parsing is complete, so that first render can avoid flash-of-partial-content problems. These are two different problems (dynamic content vs. initial render/hydration), and if components should be written to handle all of them, then they need a way to detect both of them. Otherwise, hacks will be used (again, see examples above) that will likely be broken in several cases.

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

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