Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551) from Frank Topel on 2018-10-17 (public-webapps-github@w3.org from October 2018)

From: Frank Topel <notifications@github.com>
Date: Wed, 17 Oct 2018 12:36:38 -0700
To: w3c/webcomponents <webcomponents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webcomponents/issues/551/430760304@github.com>

@justinfagnani  *The exact right combination of slotchange and and DOMContentLoaded events, MutationObserver, and connectedCallback, is just too obscure to be usable [...]*

Very well agreed. Currently it appears like you got to be a total DOM lifecycle, browser DOM implementation and consider-all-the-possible-cases guru to create robust web components relying in children. @WebReflection called it *quantum physics*, and that's exactly how you force regular developers to resort to frameworks instead of building on top of native technologies.

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

Received on Wednesday, 17 October 2018 19:37:00 UTC