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

@justinfagnani as I mentioned above, I believe it depends on the component, and the content of its shadow (and how defensive that component can be when it comes to visibility), and it our analysis, we have determined that by using detection at the first level of non-slotted/visible elements is good enough, because we haven't seen components with huge templates, it is normally a composition of other complex components.

As for scoped/lazy templates, that introduces a brand new set a problems, because the owner of the template doesn't have access or control over the instances of that template instantiated by the receiver of the template. It is just a brand new class a problems to be solved. What we are proposing is just a very small signal that can take us very far, orthogonal to the concept of scoped/lazy templates.

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

Received on Tuesday, 16 July 2019 19:59:36 UTC