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 Sep 10, 2019. It is now read-only.
The way the current motion mixins are implemented doesn't account for distinct in/out states. This is because all of the mixins transition to a null position, like so:
This works for in animations, where you're transitioning to the default state, but doesn't work for out animations, where you're transitioning away from the default state.
To correct this, each transition mixin needs a $direction property, which can be set to in or out. If the direction is out, then the mixin should start at the default state (e.g., opacity: 1, transform: translateX(0)) and transition to another state when the motion classes are added.
The text was updated successfully, but these errors were encountered:
The way the current motion mixins are implemented doesn't account for distinct in/out states. This is because all of the mixins transition to a null position, like so:
This works for in animations, where you're transitioning to the default state, but doesn't work for out animations, where you're transitioning away from the default state.
To correct this, each transition mixin needs a
$direction
property, which can be set toin
orout
. If the direction is out, then the mixin should start at the default state (e.g.,opacity: 1
,transform: translateX(0)
) and transition to another state when the motion classes are added.The text was updated successfully, but these errors were encountered: