Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909)

There's also also this for people to play around with various interpretations and, hopefully actually try to use them and live with them for a while and come back and share experiences. 

 https://github.com/bkardell/shadow-boxing
 
I can share, for example, that I had a solution very much like nolan's (called 'component-pull-marked' mode in the above) I used sporadically for a couple of years (we were very early adopters of wc) and I found it... ok as long as I was writing those components. But otherwise, as a page author it's impossibly limiting and frustrating because you can basically only do this with elements that subclass an non-standard, not already popular interface - which basically translates to "only the components I/we write ourselves".  

Very often, in practice, you get handed someone's implementation of tabs or range sliders or whatever - they might even come with a product you use... And while it's great that you can't _accidentally_ break things, sometimes you just want to say "yeah, ok, but those buttons need these styles to match my theme" regardless of who wrote it, and I guess if it breaks later I'll have to adjust - just like I do with every other library on the web.  There are also plenty of cases where what is in shadow dom is plain, it's not even a secret - a markdown component, for example - and I'd like to get one and say "ok, but apply my basic styles to the generated code".

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/909#issuecomment-1870639406
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/909/1870639406@github.com>