Re: [w3c/webcomponents] Shadow tree encapsulation and Element Timing (#816)

@domenic I can concur from a real usage perspective. At ING we've been using web components for the past 3 years doing both (1) and (2). 

We have a web component based design system for leaf components, buttons and date pickers etc. But we also use web components all the way up the tree as a component model for higher level components. Both are built by different teams with a different focus/specialty and with different requirements. For the higher level components style encapsulation is the primary reason for using shadow dom, so that different teams can easily distribute components including styles. Losing out on things like element performance timing because of that would be a shame.

To me closed/open shadow roots always seemed like the intended way to differentiate between the two use cases. 

-- 
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/816#issuecomment-502246705