Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)

I think there are two main cases:

- Styling elements that do not otherwise need a shadow root

  We've encountered a number of elements that create a shadow root only to apply host styling. Their shadow only consists of a <style> and <content>. The cost of the shadow root definitely shows up when performance tuning large apps. With this we can eliminate the shadow.

- Sharing styling across elements

  Currently this requires creating a <style> element in each shadow, which has costs. Allowing styles to be passed in as a string at definition time is a path to allowing constructible stylesheets to be passed in later.

Additionally, it may address parts of #426 by allowing elements to set `display:` at definition time, without needing to create a shadow root. This is really just the first use case, and it probably doesn't address the default value without some helper adding in `display: block` value by default.

@sorvell any more from the Polymer customers?

---
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/468#issuecomment-214915087