value-keyword-case for currentColor in non SVG CSS is breaking code

What steps are needed to reproduce the bug?

I have a CSS declaration like this:

.footer a {
  color: currentColor;
}

which gets reported as value-keyword-case error.

What Stylelint configuration is needed to reproduce the bug?

{
    "rules": {
        "value-keyword-case": [ "lower", {
            "ignoreProperties": [ "@font-stack", "font-family", "font" ]
        } ]
    }
}

How did you run Stylelint?

CLI via npx stylelint assets/css/

Which version of Stylelint are you using?

14.3.0

What did you expect to happen?

no warning or error because of the syntax correct value currentColor

What actually happened?

assets/css/…
 4:19  ✖  Expected "currentColor" to be "currentcolor"  value-keyword-case

When set to non camelCase, browser will not respect this value, which breaks the styling.

Does the bug relate to non-standard syntax?

No response

Proposal to fix the bug

The root of this issue may lay in #5849. Please take a closer look.

[jeddy3]

Closing as no further reports.

The recommendation is to use currentcolor from the CSS Level 4 spec.

[portfolioris]

I’ve found the following:

• Firefox’s devtools autocomplete to currentColor, but accepts both,
• Edge’s devtools autocomplete to both currentColor and currentcolor,
• Webstorm autocompletes to currentColor,
• MDN mentions both ways on different pages,
• The spec says currentcolor

I think the spec is the most accurate, and browsers and IDEs need to catch up.