- From: Mayank <notifications@github.com>
- Date: Fri, 12 Jan 2024 12:00:11 -0800
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 12 January 2024 20:00:17 UTC
Here's a couple stories from my own experience: - "As a component author, I want to build _unstyled_ components that only manage _behavior_. I want to give my consumers full control and achieve maximum compatibility with their existing styling solutions. I am ok with the tradeoff that DOM changes can break consumer's styles." - "As a website author, I want to use shadow DOM for my own components (that I author and consume myself). I want to use my existing CSS system, including any global resets, utility classes, and hand-rolled scoped classes. Crucially, I want these styles to be usable in DSD without causing FOUC." --- > Supporting descendent selectors that cross shadow boundaries would be significantly more complex than what I'm proposing here. Although not exactly the same as descendant selectors, I think it would be useful if some pseudo-classes like `:focus-within` and `:has(:focus-visible)` worked across shadow boundaries. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/909#issuecomment-1889878661 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/909/1889878661@github.com>
Received on Friday, 12 January 2024 20:00:17 UTC