Masafumi Koba

@emmacharp Thanks for the proposal with the reproducible demo. Adding the new option sounds good to me. 👍🏼 > Maybe the same fix as this ? #7417 I think so....

Sorry, I missed the issue. I've labeled the issue as **ready to implement**. Please consider [contributing](https://stylelint.io/contributing) if you have time. There are [steps on how to add a new option](https://stylelint.io/developer-guide/rules#add-an-option-to-a-rule)...

> Should we have a policy that states that we have to wait for the experimentation to end before we add support for such features? It seems ideal to me,...

No. My concern is how we can achieve this goal. It would be great if there was a nice solution.

Make sense. Then, do you assume such a new policy to document? For example, adding an item to "A rule must be:" etc. https://github.com/stylelint/stylelint/blob/f44de2e414b9e70cba3477e50c67e41ad97b0375/docs/developer-guide/rules.md?plain=1#L11-L14

I think the rule criteria are more suitable than the maintainer guide because this proposal is specific to the rule rather than triaging issues. If we can resolve the downsides...

@firefoxic Thanks for the proposal. Very interesting to me. Before looking into this issue and `@charset`, I didn't know the at-rule was deprecated. The following MDN documents say: - https://developer.mozilla.org/en-US/docs/Web/CSS/@charset...

> if it really is deprecated Yes, this matters. We want the rationale of this deprecation, maybe somewhere in CSS specs?

Thanks. These MDN docs seemed to be updated by PR https://github.com/mdn/content/pull/31076

@romainmenke Thanks for the effort. I now understand the syntax spec. But I still wonder if `@charset` would be necessary or often used in modern CSS programming. 🤔 I understand...