Romain Menke

Sorry, I should have clarified. What is the behavior/message without making any changes, so also without adding `local-pkg` to check if Typescript exists and emitting a custom message.

Thank you for splitting this out @jeddy3 I think this should indeed warn: ```css a { color: red; & { background: green; } } ``` But this should be fine...

> (I assume this behaviour predated the introduction of [nested declarations rules](https://drafts.csswg.org/css-nesting/#nested-declarations-rule) into the spec?) Indeed :)

Those are not redundant and actually have very specific behavior. They represent: ```css :scope.foo { } :scope .bar { } ``` But with the specificity of `:where(:scope).foo {}`, `:where(:scope) .bar...

A top level `&` is equal to `:scope` but without the specificity. And a top level `:scope` is equal to `:root` (in most cases). So `&.foo` only matches `` See:...

Thank you for the feedback @jeddy3 and @ybiquitous 🙇 I opened a new issue to discuss this aspect: https://github.com/stylelint/stylelint/issues/8906 Please take a look when you have time 🙇

Also important to consider that we can't easily add support for `languageOptions.nesting` in new rules in a patch/minor update. Users that set `languageOptions.nesting: 'standard'` while also depending on the `nonstandard`...

Thank you both for working on this @ybiquitous and @jeddy3 🙇 I really like the distinction between rules for semantics or for syntax.

There has been some movement on this in mdn browser compat data. Relevant links: - webview community group: https://github.com/WebView-CG - mdn adding data for `webview_ios` : https://github.com/mdn/browser-compat-data/pull/23747 - list of...

Aha, I wasn't aware of the prose in that section. Thank you for finding this 🙇 Unfortunately we can't parse prose 😛 > Two-component values remain invalid when specifying circle...