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

@WebReflection 

Comments on your comments:

4. in *empty custom elements* a `childrenAvailableCallback`, as the name implies, doesn't make much sense anyway. As far as I can see you can simply extend `HTMLElement` instead of `HTMLBaseElement` in that case.

5. Then how would you address asynchronous adding of child elements?

What is still open with this solution is to adjust it for use in customized-built-ins that have expectations about their children.

-- 
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-431326787