What I'm hoping to gain from this question is an idea of what those who are in the trenches believe is/are the best practices for styling web components (taking into account future specs).
There seems to be two competing philosophies in terms of styling web components. On one hand, we have the philosophy that all web components should encapsulate all their styles and you should not allow style sheets to penetrate them (aka. a style guide). On the other had, there's the philosophy that shared / common styles should penetrate web components so a style guide on a site can style them. At the moment, penetrating web components with a style sheet is difficult and not performant, but the [constructable stylesheet proposal](http://tabatkins.github.io/specs/construct-stylesheets/) would fix those issues. However, encapsulated styles for web components could also be problematic as the more styles you put in a web component, the slower it is to parse every time it's used. So taking into account the probable future, which philosophy do you believe is or will become the best practice? As a secondary discussion: do you believe you would implement paper-styles the same way if constructable stylesheets were implemented? I.E. would you still encapsulate the paper styles inside of their web components or would you create a global style sheet that the paper web components would use (not just a style sheet full of variables)? Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/60833755-8be6-492d-913d-b237551f24e3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
