- From: vmpstr via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Feb 2024 18:17:10 +0000
- To: public-css-archive@w3.org
I think the confusion here, at least it was for me initially, is that we're not talking about the specificity of the argument inside `::view-transition-*` pseudos, but rather the specificity of the pseudo itself given different types of arguments. So it does play in the regular space. I agree that in the pseudo space, the solution is pretty simple: id is id-like and each class is class-like. When bringing that to the regular space, there needs to be some mapping. One idea that came up is to maybe introduce another tie-breaker category of specificity. That is, instead of `id-like, class-like, type-like` have `id-like, class-like, type-like, argument-tie-breaker-like` in that order. That way, all of the specificity ordering is somewhat independent of the argument, unless there's a tie. In case of a tie, we look at the argument -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9887#issuecomment-1924439582 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 February 2024 18:17:12 UTC