- From: Ryosuke Niwa <notifications@github.com>
- Date: Tue, 19 Mar 2019 14:40:10 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 19 March 2019 21:40:31 UTC
> Hey Ryo, the use case is presented, in the above 2nd fiddle. Wanting to detect when a custom element is created by a fragment parsing algorithm is **NOT** a use case. Wanting to have a guarantee that each child has been upgraded before accessing it is **NOT** a use case. A use case is a specific user scenario. > It's not clear how to detect or work with children in that case, in order to run logic on any/all upgraded children in a guaranteed way like we can with initial-payload parsing in the the 1st fiddle. Like I've stated dozens of times, with the current custom elements API, you'd need to have a child talk to its parent, not a parent finding the right kind of 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/789#issuecomment-474595292
Received on Tuesday, 19 March 2019 21:40:31 UTC