-
Notifications
You must be signed in to change notification settings - Fork 686
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
Remove transition-duration style after move? #4
Comments
ah, yeah that sounds like a bug to me |
Oh, I just sent a pull req on this which was just merged: Perhaps this issue can be closed now? |
Hmm, been awhile since I looked at this. Strictly speaking the merge didn't include transition-duration, just transition and transition-property. Move also uses transition-timing-function and a few other ones. Also, shouldn't the state of the element be restored to whatever it was, not necessarily null? Perhaps the best thing would be to store those at the start (and potentially remove them so they don't interfere with what Move does) and then put them back at the end. Move would then also be side-effect free after being run. |
This is still a bug. Currently working around it with a bit of a hack. Any time I use move.js, I have to append this to an animation.
This is needed to avoid an unwanted trigger of the animation when later changing the css attributes after having already done an animation with move.js. It would be nice to be able to destroy an instance of move.js, or at least have the duration removed. |
I have a situation where I animate button, and after animation I want the button to have CSS hover animation.
Now I cannot achieve this because the animation duration style properties are set to '0ms' in this line: Line 515 in 879feca
I fixed this by setting the style properties to empty string instead of |
I created a quick pull request of how I fixed it myself. There might be other scenarios where my fix does not work at all. |
After completing a move animation, the [-vendor]-transition-duration style is still on the element, which will alter other interactions outside of move.js. Current workaround is to remove it by passing callback to final end().
Perhaps the top-level end() should remove this style as part of move.js?
The text was updated successfully, but these errors were encountered: