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 am trying to achieve a morphing animation between views using ng-animate-ref. The animation should follow the steps below:
When the user clicks the element to go forwards or the back link to go backwards, Fade out the contents of the element by transitioning the opacity of the contents.
Morph the element into it's new size and position using ng-animate-ref.
Either fade out the cloned element to reveal the actual element underneath or fade in the actual element when the cloned element is removed from the dom.
It is the 3rd step that I cannot achieve. Here is a plunkr with what I have so far.
The problem I have is that ng-anchor-out-remove happens too early (during the morph) and then there is no ng-animate-shim-remove on the real element that I could use. I can't think what else to do.
The text was updated successfully, but these errors were encountered:
I am trying to achieve a morphing animation between views using ng-animate-ref. The animation should follow the steps below:
When the user clicks the element to go forwards or the back link to go backwards, Fade out the contents of the element by transitioning the opacity of the contents.
Morph the element into it's new size and position using ng-animate-ref.
Either fade out the cloned element to reveal the actual element underneath or fade in the actual element when the cloned element is removed from the dom.
It is the 3rd step that I cannot achieve. Here is a plunkr with what I have so far.
http://plnkr.co/edit/H41tfHjpmK6o5jm2XhoE?p=preview
The problem I have is that ng-anchor-out-remove happens too early (during the morph) and then there is no ng-animate-shim-remove on the real element that I could use. I can't think what else to do.
The text was updated successfully, but these errors were encountered: