Masafumi Koba

@firefoxic @romainmenke Thanks for your kind explanation. I understand the necessity to lint `@charset`. 👍🏼 However, I still wonder whether we should implement the new rule and include it in...

Okay, there seems to be some rationale in the new rule. Additionally, I'd like to clarify a few more things: - Complexity in implementation (may cause bugs) - Performance (may...

@hudochenkov Thanks for the report. Right, this is a bug of false negatives. > Update [shorthands reference](https://github.com/stylelint/stylelint/blob/328544d8dfe4abfb1d75ab6631528f2e3c605a74/lib/reference/properties.mjs#L15). This update only may not be enough. It may be necessary to fix...

@emmacharp Thanks for the report with a reproduction. To clarify, do you want to disallow a `width` prop within all `input` selectors? I created the [online demo](https://stylelint.io/demo/#N4Igxg9gJgpiBcIB0BnGBDATmAFgAmAB0A7PPAMjwEtiAHAVwBcCSyyB3KqRnePARgAMggKQBuVngC+JGcRKoM2fDQbMipPJ268Bw8bJIgANCABmVADYwAcugC2cRDAAeD2taRgUKE+AjEFgDmCCAaZIQgmPTWKJF84WyR0dYAtGjWYIwQmKm0mBC0MJiMAJ6pUFQo6JaWEOwwUKmWVYzxeADawHiRqkztkdo8kdIAupJyUn6QgVRBAGI59uiMoQBWKAF+sLS+iImRKGXWLcRtCD0gliswR5GyIFJAA), which doesn't seem...

Ah, I understand it now. See the new [demo](https://stylelint.io/demo/#N4Igxg9gJgpiBcIB0BnGBDATmAFgAmAB0A7PPAMjwEtiAHAVwBcCSyyB3KqRnePARgAMggKQBuPAHoAVHhQ4I9ADZQ8AIxh4IAawA06pnnRhG9dEqUBPPJhi0ImRjFXTJrPAF8SX4iVQZsfBoGZiJSPE5uXgFhcSlZYghmW3tHZ30dPFdvEj80LFw8ADMHAFsWcMiePiFRCRkbOwcnKAztLLdiDxBdECKqJRgAOXRSuEQYAA9R2kGkMBQUHvAIYn6AcwQQMLJCEExlGBQ9vh22PYPBgFo0QZMHK9pMCFoYR0srqCoUcyUIdmcVyU30YJzwAG1gHg9pIAHoACnhAH4AITBJgASiQGOkABI3AhoSAqjg9p4ALruHzdXqQNZUdYAMTK6EYWwAVihVstYLQlogznsUIxLINgcRQYS9kpWUdJd4QB4gA). ```css .search { & input { width: 100%; /* should be ok, but actually reported */ /* ^^^^^ Unexpected property "width"...

I've updated this issue body to include the correct reproduction and the online demo.

We can use [`postcss-resolve-nested-selector`](https://www.npmjs.com/package/postcss-resolve-nested-selector) to resolve a nested selector, which is installed already. Otherwise, we may be able to install and use [`@csstools/selector-resolve-nested`](https://www.npmjs.com/package/@csstools/selector-resolve-nested) instead. The package follows the CSS Nesting...

Ah, I see. Don't mind. Adding `@csstools/selector-resolve-nested` was started with PR #7496, so let's wait for the job. This issue should be addressed more easily if the job is done.

In this issue, I favor installing `@csstools/selector-resolve-nested` because #7496 tries replacing `postcss-resolve-nested-selector` with `@csstools/selector-resolve-nested` but `rule-selector-property-disallowed-list` doesn't rely on `postcss-resolve-nested-selector`. There is no breaking change when using `@csstools/selector-resolve-nested`. CC: @romainmenke...

@emmacharp Thanks for the proposal. Sounds interesting to me. Like the [`message` secondary option](https://github.com/stylelint/stylelint/blob/eebb78694ee87e76245414108b0ae2626c78729f/docs/user-guide/configure.md#message), a new option (e.g. `url`) seems to be as follows: ```js const config = { rules:...