Re: [csswg-drafts] [css-nesting-1] Ambiguity of specificity when no nesting selector is used (#9069)

Yeah, but if an author writes:
```
.foo .bar,
#foo .bar { ... }
```
They get the equivalent behavior of:
```
.foo .bar { ... }
#foo .bar { ... }
```
right? e.g. two rules with different specificity that cascade independently

If 
```
.foo,
#bar {
  .bar { ... }
}
```
behaves like one rule with a single specificity, then this is an author foot-gun and will cause all sorts of cascading bugs, especially when people refactor existing stylesheets in to nested ones.

I understand it complicates the implementation, but the behavior is not identical and author needs win over implementer needs.

Discuss this at the F2F?

-- 
GitHub Notification of comment by plinss
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9069#issuecomment-1639077177 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 18 July 2023 00:21:55 UTC