Re: [w3c/webcomponents] Consider adding a childrenChangedCallback or something (#619)

I've implemented this myself, and basically https://github.com/w3c/webcomponents/issues/668 makes it very difficult to get it just right.

For instance, during parsing, the order of `connectedCallback` calls in a tree of elements is from parent to leaf-most child. However, the order of `connectedCallback`s when using `innerHTML` or just waiting for the document to be ready before defining elements is from leaf-most child to parent (backwards!).

These sort of inconsistencies make it difficult to write clean programs.

In React, Vue, Angular, etc, the order of callbacks are guaranteed. People coming from those libraries will stumble on this.

-- 
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/619#issuecomment-335045453