@justinfagnani the `childrenChangedCallback` is an easy peasy thing to configure in the `constructor`, if needed, so it's way easier to have and definitively less important than `parsedCallback` / `buildCallback`, IMO. > `finishedParsingChildrenCallback` doesn't solve the dynamically changing children case. anything specific to children doesn't solve much, and children are super easy to observe already. > The platform should provide a reasonable signal for "If I need to process children, when should I do it". For one-off setup that is exactly what `parsedCallback` / `buildCallback` are being proposed. For anything else, if needed, we already have MutationObserver, I don't think we should slow down everything with an implicit mutation observer for children in every custom element. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/551#issuecomment-430674691
Received on Wednesday, 17 October 2018 15:28:03 UTC