Re: [w3c/webcomponents] Discussion: child elements cannot determine whether they are "active" or not (#817)

@caridy I think Rich's criticism is more about laziness than visibility or connectedness. In many "over the top" frameworks you can give a component some children, and that component can decide whether or not to even create the DOM for those children. With web components, if a component has children, they're necessarily already instantiated.

I think the solution there is to recognize that `<template>` is the lazy operator for HTML. A component can receive template children and clone them on demand.

-- 
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/817#issuecomment-511923466