- From: robglidden <notifications@github.com>
- Date: Fri, 01 Mar 2024 14:09:14 -0800
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <WICG/webcomponents/issues/909/1973994043@github.com>
@bkardell As I alluded to, declarative shadow DOM has changed my approach to web components, and I now use it as the main path to broadening the usefulness of shadow trees. So my starting answer for designing web components that support styles they don't control is to design HTML-first with declarative shadow DOM. It works great, and imperative-first is still fine for what it is best at. From there, I need to address: - component user who wants to style inside a shadow tree - component designer who wants to selectively let in outer styles with control For me, "[all the complexity and all the opt-in is within the component definition](https://github.com/WICG/webcomponents/issues/909#issuecomment-1951970599)" for *both* of these use cases, and declarative HTML-first web component design already gets me a good way there. In other words, "[the component user does not need to do absolutely anything (besides including and using the component)](https://github.com/WICG/webcomponents/issues/909#issuecomment-1952937020)" For me, access to and prioritization of outer style layers inside shadow trees would address both use cases, and an enabling tool would be helpful along the way. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/909#issuecomment-1973994043 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/909/1973994043@github.com>
Received on Friday, 1 March 2024 22:09:18 UTC