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

Relaxing Shadow DOM encapsulation? I've had strong opinions both ways. But I have a new understanding now as I've eventually found that many of these pain points aren't even a Web Components'/ Shadow DOM's call. 

For example, should basic things like style scoping and ID/IDREF scoping really warrant a Shadow DOM? (Look how many years it has taken to realise the answer to the first- in the return of scoped CSS, i.e. `@scope`.)

What I see is clear appetite to have most of these features *outside* of the Shadow DOM, i.e. in the open HTML/DOM land. And my new belief is that the Shadow DOM might be just already great for the *right* use cases, assuming we find outside answers to the more common non-shadow scenarios, as we're now doing with scope styles.

Put another way, haviing the Shadow DOM as the one means to those ends is what I see as the problem.

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

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