- From: Steve Orvell via GitHub <sysbot+gh@w3.org>
- Date: Tue, 15 Oct 2024 00:09:05 +0000
- To: public-css-archive@w3.org
> It doesn't seem to me like it's reasonable for some CSS to define what other CSS is allowed to style. This is exactly what I was hoping was being proposed here. I recognize it seems like an exotic concept, but the existence of Shadow DOM style isolation shows that it's valuable in principle. And yes, that is dictated by the shape of the DOM, but it's exactly this restriction that makes it unwieldy and problematic. Zooming out, CSS decouples styling from the DOM. It uses information in the DOM but it's not really limited by it (I can select a class or a tag name or an id etc.). New concepts like @scope selectively apply rules to portions of the DOM and @layer provides explicit control over the order of the cascade. The isolation concept seems like a potentially logical next step. Decoupling isolation from an intrustive DOM feature (Shadow DOM) would be more expressive and flexible. If there's not some fundamental reason it's antithetical to the core design of CSS, it seems at least worth considering? -- GitHub Notification of comment by sorvell Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11002#issuecomment-2412561568 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 15 October 2024 00:09:06 UTC