-
Notifications
You must be signed in to change notification settings - Fork 320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash with animation properties #941
Comments
Hi @mikestreety - this is an output I get with 4.1.1: li{animation:.4s ease-in .2s introGrow} Could the problem lie somewhere else? |
@jakubpawlowicz Thanks for the quick reply. I tried the It's interesting you get that output. I've had the same thing on a different project, with the same |
You should be able to workaround the issue by using Would you be able to share, either publicly or privately, a bigger excerpt of your CSS so I can try to replicate this bug locally? |
Coincidentally, I came upon this same exception, and it turns out to be a problem with .abc {
-webkit-animation: something 0.5s 1 ease-in-out;
-webkit-animation-fill-mode: both;
} |
@ngyikp looks like it! 👍 |
Ah yes! I autoprefix before I run it through clean-css. That must be it!
|
Thanks @jakubpawlowicz |
The fix is out in 4.1.2. |
Hello.
When I use
animation
&animation-*
properties together, I get a crash on level 2 optimisations. I currently usegulp-clean-css
but this seems like an isse withclean-css
itself. It looks similar to #940This error can be skipped by combing the animation properties for now.
Error:
Expand to see the error
Environment
Expand to see the environment
npm ls clean-css
:node -v
:Configuration options
Adding
skipProperties: ['animation']
does not workInput CSS
animation-delay
is calculated by SCSS and process before being run throughclean-css
. The reason this is split out is for readability.Actual output CSS
None, it crashes
Expected output CSS
The text was updated successfully, but these errors were encountered: