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

As a developer i expect, that all dom structure parsed and accessible in connectedCallback. 
CEReaction for element must starts only after parent element finished his connectedCallback event. Because parent can fully change his content.
connectedCallback must behave as connectedAndParsedAllChildrenCallback. 

If component has child nodes but they inaccessible, connectedCallback is absolutelly useless for developers without children content.
Now all implementations connectedCallback behave as connectedAndParsedAllChildrenCallback. I dont't understand why new specification modify it.

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