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
Progress callback only called in the first animation loop #292
Comments
@raphaelrauwolf thanks! That's correct. I'm not sure, though, if the |
In the documentation, you only state that That the The real-life scenario would be : http://jsfiddle.net/5adbtywv/. |
I agree it is not the expected behavior, question is whether we support this behavior or ignore it. That's a cool use for it (: @julianshapiro IINM it's just adding another line here copying the progress callback. |
@raphaelrauwolf: I consider this a bug. Will fix, thanks. Stay tuned! |
Oops. @ydaniv: That was the right area. Lol. |
Done. Coming up in the next release. |
Please check, make sure it works, and get back to me. Thanks! |
Works fine! Thank you! http://jsfiddle.net/5adbtywv/2/ |
I think the problem of ingoring the |
Internal “Sequences” have been renamed to “Redirects”. You shouldn’t have been using them (they were deprecated), so this is not being considered backwards-incompatible. `Velocity.mock` now accepts a multiplier value in addition to `true`. Use it for slowing down/speeding up animations globally when testing. `true` mock has also been fixed to also reduce `delay`s to 1ms. You can now animate `filter: blur(value);` for -webkit- browsers. Note that animating this property will strip out all other `filter` components. Note that, at the time of this update, Chrome incorrectly returns blur values that were originally set with the `px` unit. `color` RGB defaults to black instead of white, which is closer to text’s typical color value. `opts.progress` now gets repeatedly fired during looped calls. Closes #292. Fix jQuery-free `position: absolute` bug with left/top properties. Closes #285. Allow passing undefined as a second arg into Velocity. Closes #275. Performance improvement: Individual property tweens don’t update the DOM if there’s no change in value between loop ticks. Fixes bug where `loop`ing on iOS devices (due to mobileHA) would cause flickering. Closes #299. Fixes bug where you couldn’t force-feed one hex value to another. Can now set `visibility: “”`, just like you can with display. Fixed bug where using `backwards: true:` with the UI pack mutated the source array.
When you loop any velocity animation, the progress callback is called only in the first loop and after that it is ignored.
The text was updated successfully, but these errors were encountered: