Re: [w3c/webcomponents] > ""::slotted() should full support complex selector"" has came up multiple time and always get closed without any solution. (#881)

> > > > So @rniwa is the recommendation that whenever you have to style slotted nested children, just make them seperate component with their own shadow dom?
> > > 
> > > 
> > > Thats also what i understood, and the first thing i tried but like said my very last message, there is a painfull snowball effect!
> > 
> > 
> > I'd like to better understand what your "painful snowball effect" is. Perhaps those pain points are things we can resolve.
> 
> No, clearly you can't. At this point of recalcitrant non-sens i'll just use another technology.

You're more than welcome to do so. Shadow DOM and custom elements aren't meant to solve every problem in existence nor was it conceptualized to address every paradigm of writing web apps or websites. If it doesn't meet your needs, using another approach is the right thing to do.

> You are suppose to be w3c, not our stubborn uncle who knows better then everyone. I do not thank you but i'll be sure to stay in touch with the others you shut down.

Please refer to [WHATWG's code of conduct](https://whatwg.org/code-of-conduct) and [W3C's code of ethics and conduct](https://www.w3.org/Consortium/cepc/). I've been following up on this issue on my spare time while I'm on a long term medical leave. I don't appreciate you name calling me like that.

> This is exactly how new technologies are born since always.

That's simply not how W3C or WHATWG operate these days. We base our solutions on use cases and problems, not an abstract need to do something.

> Your fixation on what NOT to do with web components prevent you from even reading us right.

On the other hand, you seem to be fixated on the exact solution you'd like to have. What I'd like to do is to explore alternative solutions that can address your use cases. Perhaps we'd conclude that adding the capability to style arbitrary descendants of slotted content is the only way but maybe not. Would you not rather explore those possibilities at all because you want one kind of solution?

> You just keep making us repeat and turn the question around til you win your opinion. Yes OPINION, because not once you provide an actual argument about anything. I do not believe you don't understand for one second. I chat bot would do better.

Well, it's not my opinion that supporting the ability to style any descendent of slotted content incurs unacceptable performance cost. That's a matter of fact statement we know as a browser engine implementor. And people who use web browsers care a lot about performance & responsiveness so we're constrained by that need.

And again, I really do not appreciate your tone of voice here. You've been warned.

-- 
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/881#issuecomment-632990058