- From: Xiaocheng Hu via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Oct 2022 22:10:20 +0000
- To: public-css-archive@w3.org
From my experience dealing with `@keyframes`, `@counter-style` and `@font-face`, name inheritance is quite complicated to support. I don't really see it as a convenience feature, but a workaround for backward-compatibility since browser support for tree-scoped names (for existing at-rules) have been always bad/none, and people have been relying on global at-rules. Also there are some other new features that explicitly reject inheritance for better encapsulation, like [scoped custom element registries](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md#finding-a-custom-element-definition). I'll +1 to leaving this spec as-is and modify Scoping instead. -- GitHub Notification of comment by xiaochengh Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7916#issuecomment-1287484754 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 21 October 2022 22:10:22 UTC