postcss-merge-longhand should preserve case of CSS custom properties #648
Labels
Comments
|
@p-a oh, it is bug, feel free to send a PR |
p-a
pushed a commit
to p-a/cssnano
that referenced
this issue
Oct 25, 2018
p-a
pushed a commit
to p-a/cssnano
that referenced
this issue
Oct 27, 2018
alexander-akait
pushed a commit
that referenced
this issue
Nov 1, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CSS custom properties are unlike other properties case-sensitive
postcss-merge-longhand however lowercases all properties which f.ex. turns
.foo { border: 1px rgba(var(--camelCase),1); }into
.foo{border:1px rgba(var(--camelcase),1)}The culprit seems to be parseWsc.js
Rather than bluntly lowercasing any match, it should try not to do that for custom properties.
I guess an easy workaround would be to just bailout if the string includes two consecutive dashes.
The text was updated successfully, but these errors were encountered: