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 was archived by the owner on Apr 12, 2024. It is now read-only.
I have a case that need to apply different animation style to a dynamically generated content that enter/leave the scene. The animation is defined in CSS like:
The problem is that if once the transition style has no animation (i.e. $scope.transitionStyle = ''), it will be remembered and the following change to transition style (e.g. $scope.transitionStyle = 'slide-left') cannot be applied.
Please check this plunker, if you click 'slide left' or 'slide right' first, the animation is fine. After you have clicked 'no style', the will be no animation even if you click 'slide left/right'.
Normally, I should apply the style to the dynamic content itself. But in this case the the dynamic content is generated and enter/leave by 3rd party library (ui-router) which I have no control over.
The text was updated successfully, but these errors were encountered:
I have a case that need to apply different animation style to a dynamically generated content that enter/leave the scene. The animation is defined in CSS like:
The html would be
When add/remove content, the following is called
The problem is that if once the transition style has no animation (i.e.
$scope.transitionStyle = ''
), it will be remembered and the following change to transition style (e.g.$scope.transitionStyle = 'slide-left'
) cannot be applied.Please check this plunker, if you click 'slide left' or 'slide right' first, the animation is fine. After you have clicked 'no style', the will be no animation even if you click 'slide left/right'.
Normally, I should apply the style to the dynamic content itself. But in this case the the dynamic content is generated and
enter/leave
by 3rd party library (ui-router) which I have no control over.The text was updated successfully, but these errors were encountered: