- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Oct 2023 17:21:02 +0000
- To: public-css-archive@w3.org
The problem is basically the same as in #1027
```css
#a1, .a2, a3 {
& #b1, & .b2, & b3 {
& #c1, & .c2, & c3 {
& #d1, & .d2, & d3 {
& #e1, & .e2, & e3 {
& #f1, & .f2, & f3 {
```
Very short, but there are 729 possible different ways to match this. If the specificity can vary, then it has a performance impact, e.g. knowing that the element matches `.a2 .b2 .c2 .d2 .e2 .f2` is not enough, because maybe it also matches `a3 #b1 .c2 d3 .e2 f3` which has a higher specificity. So checking all/several possible combinations is needed.
I still don't see how the specificity concern is related to #8738. And while I can see it might be confusing, it doesn't seem inconsistent nor anything. As I said in https://github.com/w3c/csswg-drafts/issues/9492#issuecomment-1769062893, I don't see the need to change the current specificity.
@FremyCompany Your idea would imply a combinatorial explosion?
--
GitHub Notification of comment by Loirooriol
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9492#issuecomment-1779726573 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 October 2023 17:21:04 UTC