- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Apr 2024 21:31:48 +0000
- To: public-css-archive@w3.org
Right, right.
Well, it looks like the current behavior is _intentional_ at least, as @mirisuzanne and I apparently briefly discussed this June 19th, 2023 (chat history). We both concluded (from the discussion in https://github.com/w3c/csswg-drafts/issues/8500) that any implicit `:scope` should not contribute to specificity.
I also noted at the time:
> "That means `@scope (.a) { .b { ... } }` and `@scope (.a) { :scope .b { ... } }` are different rules, and we can not serialize one as the other."
So yeah, [oopsie](https://github.com/w3c/csswg-drafts/issues/9621). :-)
With both Chrome and Webkit having shipped now, a change here _could_ be too late already. I'll try to investigate that if we indeed want to change.
--
GitHub Notification of comment by andruud
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10196#issuecomment-2048470909 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 April 2024 21:31:49 UTC