- From: Bramus! via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Jul 2023 17:30:06 +0000
- To: public-css-archive@w3.org
Spec currently reads this _([source](https://www.w3.org/TR/css-cascade-6/#:~:text=Global%20name%2Ddefining))_: > Global name-defining [at-rules](https://www.w3.org/TR/css-syntax-3/#at-rule) such as [@keyframes](https://www.w3.org/TR/css-animations-1/#at-ruledef-keyframes) or [@font-face](https://www.w3.org/TR/css-fonts-5/#at-font-face-rule) or [@layer](https://www.w3.org/TR/css-cascade-5/#at-ruledef-layer) that are defined inside [@scope](https://www.w3.org/TR/css-cascade-6/#at-ruledef-scope) are valid, but are not scoped or otherwise affected by the enclosing @scope rule. Probably makes sense to keep this behavior, and make it an opt-int should we want to. Use-case would be an author shipping a component with scoped styles, knowing that the custom properties they use don’t clash with the global namespace. Right now they need to work around this by prefixing their custom props, hoping nobody else uses that prefix. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9077#issuecomment-1640663808 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 July 2023 17:30:08 UTC