You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 27, 2021. It is now read-only.
I'm really enjoying working with FLIP! Thanks for the write-ups and demos.
Wondering what the most effective way of chaining animations to fire on an element sequentially would be. Request for complete callback would get us part of the way there, but wondering if there's something else at an API level that could be explored? Would love to hear your thoughts.
Cheers
The text was updated successfully, but these errors were encountered:
Thanks. The flipComplete will tell you which/when element has finished FLIPing, but not which animation has just finished. For example, if I had a single element which could be FLIP'd in a few ways sequentially (.flip-left, .flip-down and .flip-fade), the only way of telling which has just happened is to check the FLIP or element target's classList.
From there, I guess you could infer and FLIP the next intended animation? Starts to get hairy once there's more than a couple of FLIPs involved. I may be missing an obvious solution here...
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm really enjoying working with FLIP! Thanks for the write-ups and demos.
Wondering what the most effective way of chaining animations to fire on an element sequentially would be. Request for
complete
callback would get us part of the way there, but wondering if there's something else at an API level that could be explored? Would love to hear your thoughts.Cheers
The text was updated successfully, but these errors were encountered: