Re: [WICG/webcomponents] Shadow DOM mode as opt-in feature flags (Issue #1049)

@ox-harris I agree with you that having Shadow DOM as the only option for many of the features it provides is an issue. I'm very happy to see the return of `@scope` and would love to see more progress in that way (can we get a second act for `@apply`?). But I don't think introducing the feature flag idea to Shadow DOM precludes that progress from continuing. My concern is the number of new features that keep getting added to other specs to work around encapsulation rather than just allowing the encapsulation to be opt-in. I see `::part` and `::slotted` as really unfortunate and some of the other proposals of messing with `@layer` or introducing new selectors like `/shadow/` as complexity on top of complexity rather than eliminating complexity. I want fewer features, not more.

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

Message ID: <WICG/webcomponents/issues/1049/1939709059@github.com>