We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Not a serious bug, but more of a degradation
npm ls clean-css
node -v
const CleanCSS = require('clean-css'); const fs = require('fs'); const input = fs.readFileSync('test.css', 'utf-8'); console.log(new CleanCSS().minify(input).styles);
.a {background-image:linear-gradient(to top, #AABBCC, #ffffff);} .b {background-image:linear-gradient(to top, #AABBCC, #FFFFFF);}
.a{background-image:linear-gradient(to top,#abc,#ffffff)} .b{background-image:linear-gradient(to top,#abc,#fffFFF)}
.a,.b{background-image:linear-gradient(to top,#abc,#fff)}
Hex colors in gradients are failing to shrink and some weird capitalisation if they are uppercase.
The text was updated successfully, but these errors were encountered:
This is weird indeed. Thanks for catching it!
Sorry, something went wrong.
Fixes #959 - regression in shortening long hex values.
0f2d4fb
Introduced in #945.
c1aad92
f4f54cf
Thanks @ngyikp, it's fixed in 4.1.8.
No branches or pull requests
Not a serious bug, but more of a degradation
npm ls clean-css
: 4.1.7, but regressed since 4.1.5, most likely gradient color value will be optimized in the filter #945node -v
: v8.1.4Configuration options
Input CSS
Actual output CSS
Expected output CSS
Hex colors in gradients are failing to shrink and some weird capitalisation if they are uppercase.
The text was updated successfully, but these errors were encountered: