- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 17 Jul 2023 23:15:14 +0000
- To: public-css-archive@w3.org
Yeah, if the nesting selector is implied, it should still have an effect on specificity, same as if it was written explicitly. I'll fix the spec. (This matches the serialization behavior we decided on last week.) @plinss We decided against that behavior in `:is()` because it drastically complicates the implementation - you have to track which virtual selector was matched (where the number of virtual selectors are multiplicative in the number of `:is()` selectors. The effect with Nesting is identical, so we went with identical behavior. (This does differ from preprocessors that decompose nested selectors directly, but we fundamentally can't match that without running into this explosion/complexity issue.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9069#issuecomment-1639018299 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 17 July 2023 23:15:16 UTC