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
First of all, congratulations on Micromodal. It's simple, lightweight and allows customization of the modal.
Our team has an experience to share:
If there is more than one animation running, Micromdal only recognizes the one that finishes first and ignores the others.
Example: when clicking on the close button (awaitCloseAnimation: true), animation A (lasting 1s, no delay) and animation B (lasting 1s, delay .5s) are triggered, then the modal closes on end of animation A interrupting animation B in half. To prevent this from happening, we are forced to finish the animations at the same time.
Also, we want to suggest better documentation.
The text was updated successfully, but these errors were encountered:
First of all, congratulations on Micromodal. It's simple, lightweight and allows customization of the modal.
Our team has an experience to share:
If there is more than one animation running, Micromdal only recognizes the one that finishes first and ignores the others.
Example: when clicking on the close button (awaitCloseAnimation: true), animation A (lasting 1s, no delay) and animation B (lasting 1s, delay .5s) are triggered, then the modal closes on end of animation A interrupting animation B in half. To prevent this from happening, we are forced to finish the animations at the same time.
Also, we want to suggest better documentation.
The text was updated successfully, but these errors were encountered: