Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587) from thecodejack on 2018-12-20 (public-webapps-github@w3.org from December 2018)

From: thecodejack <notifications@github.com>
Date: Wed, 19 Dec 2018 23:21:14 -0800
To: w3c/webcomponents <webcomponents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webcomponents/issues/587/448899001@github.com>

I got your point of element insertion or removal but there is high probability the MutationObserver runs multiple times if there are multiple children that are active. Anyways I don't think need for lifecycle event after children being ready is a flaw. Even many major frameworks react (componentDidMount), vue (mounted), angular (afterView/afterContent) provides you similar functionality. 

-- 
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/587#issuecomment-448899001

Received on Thursday, 20 December 2018 07:21:37 UTC