Re: [w3c/webcomponents] Theming options for shadow roots (#864)

@justinfagnani 
Thanks for taking the time to explain why/when encapsulation of styles is useful. I think it makes perfect sense, especially when working all "leaf" components and in larger orgs.
I just wanted to raise awareness (and I promise this is my last pseudo-philosophical post) that we are about to change the platform with webcomponents and in the long term this may not only affect the way webapps are built, but also how websites will be build (by mashing up webcomponents from different sources). As such we have to be careful not to take away the remaining playground for people that are incompatible with large orgs and still want to make a living from creating web pages by restricting the way things are supposed to be used (blackboxing).
So I still think a master-switch that opens a webcomponent and at the same time voids the warranty of the author or other mechanisms to override the internal styles (e.g. !super-important flag in css) may be a good thing to allow creative use that has not been intended by the author:
https://www.youtube.com/watch?v=jKv_N0IDS2A
Styling should be simple enough for ordinary people (who understand how to use .myclass and #myelement but not how to use .myclass .mynestedclass etc.). Smart people and large orgs have taken almost the entire cake over the past decades, so at least some crumbs should be left for the rest.

-- 
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/864#issuecomment-592517867