- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Tue, 25 Jun 2024 18:09:31 +0000
- To: public-css-archive@w3.org
The proposal here is to treat directly-nested declarations in a scope rule such that:
- they apply to the `:scope` element
- no specificity is added
That is, as though the declarations are wrapped in `:where(:scope) { /* declarations */ }`
---
- This comes out of our previous resolution (https://github.com/w3c/csswg-drafts/issues/10196#issuecomment-2161119978) that an implicitly added `:scope` wrapper on scope-nested rules should not impact specificity. Which requires us to revert/clarify how that implicit `:scope` is serialized (https://github.com/w3c/csswg-drafts/issues/9621#issuecomment-1864891688)
- This would also resolve https://github.com/w3c/csswg-drafts/issues/10389, since it means we are allowing bare declarations inside a scope rule.
I would like to resolve all three aspects of this at once if we can:
- #10389 Resolve to allow bare declarations in `@scope`
- #10431 (this issue) Bare declarations apply to the `:scope` element, without additional specificity
- #10389 Clarify serialization of implicit `:scope`, so no implicit specificity is added
--
GitHub Notification of comment by mirisuzanne
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10431#issuecomment-2189648413 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 25 June 2024 18:09:32 UTC