Masafumi Koba

So, this problem seems specific to the VSCode extension. I'll transfer this issue to https://github.com/stylelint/vscode-stylelint

@dan2kx When I change `editor.formatOnSave` from `true` to `false`, the problem is gone. Can you try it? ```diff - "editor.formatOnSave": true, + "editor.formatOnSave": false, ```

@dan2kx I'm afraid that I'm unfamiliar with VSCode, but can you use [`editor.codeActionsOnSave`](https://github.com/stylelint/vscode-stylelint#editorcodeactionsonsave) instead?

Ah, right. Sorry, I missed the setting. I'm unsure which is the cause. 😕

Thanks for providing the reproduction. `editor.formatOnSave` and `editor.codeActionsOnSave` seem to conflict for some reason. 🤔

@GrimLink Thanks for opening the issue. I'm against removing `media-feature-range-notation: "context"` because we would need to *re-add* the rule in the future. And the removal would instead confuse other people...

Thanks for summing up. That makes sense to me. And adding the guideline as follows to README sounds very nice. 👍🏼 > "To help people write as modern as possible...

@romainmenke Thanks for your sharing Baseline. I agree with following the Baseline. 👍🏼 I guess we have two Baseline options, and we need to choose one from them: - **Widely...

I just changed the issue title.

@rohm1 Thanks for the report. But I believe this is not a bug. You can avoid the error by the [`camelCaseSvgKeywords`](https://stylelint.io/user-guide/rules/value-keyword-case/#camelcasesvgkeywords-true--false-default-false) option: ```json { "rules": { "value-keyword-case": ["lower", {"camelCaseSvgKeywords": true}]...