- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Feb 2024 18:09:09 +0000
- To: public-css-archive@w3.org
Why shouldn't the specificity just be reflected straight into normal specificity, as ID and class values? These are, by definition, not fighting with any *non*-VT styles. The only concern, I guess would be that it would mean `div::view-transition-group(foo)` would beat `.foo::view-transition-group(.bar)`, since it would be [1,0,1] vs [0,2,0]. Is that good, or bad? Switching it to a new, lowest specificity term would mean the `.foo` rule wins, and always will regardless of argument. Is either option *very likely* to be the right choice, or is it going to be a contextual decision always? Is there any potential for other functions we might want to give a weak, tie-breakery notion of specificity to? -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9887#issuecomment-1927671274 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 5 February 2024 18:09:13 UTC