-
Notifications
You must be signed in to change notification settings - Fork 27.4k
Element Anchoring Animation not starting #11681
Comments
Can you please try with the latest snapshot? https://code.angularjs.org/snapshot/angular.js |
I just tried and the same issue occurs https://jsfiddle.net/3eouz22z/4/ |
I think it's mainly a problem with your css code: https://jsfiddle.net/3eouz22z/5/ The trigger css class for anchor animations must be the class on your view + anchor:
while you had previously: |
Yes @Narretz is correct. Here is a working version of your code: http://plnkr.co/edit/NMvWx0NhGylfnRr887sC?p=preview I've been thinking about this and I think it's best that we generate the |
@geekuillaume @Narretz now a combination of both the origin/destination element classes as well as the container classes are prefixed and applied to the anchor element. #11822 |
…re retained This patch ensures that all of the CSS classes that exist on both anchor nodes (the nodes that contain a `ng-animate-ref` attribute) are not removed from the cloned element during the anchor animation. (Previously the `in` animation would accidentally remove the CSS classes of the first element.) Closes angular#11681
…re retained This patch ensures that all of the CSS classes that exist on both anchor nodes (the nodes that contain a `ng-animate-ref` attribute) are not removed from the cloned element during the anchor animation. (Previously the `in` animation would accidentally remove the CSS classes of the first element.) Closes angular#11681
Actually, it's better that we stick 100% to using the |
…re retained This patch ensures that all of the CSS classes that exist on both anchor nodes (the nodes that contain a `ng-animate-ref` attribute) are not removed from the cloned element during the anchor animation. (Previously the `in` animation would accidentally remove the CSS classes of the first element.) Closes angular#11681
…re retained This patch ensures that all of the CSS classes that exist on both anchor nodes (the nodes that contain a `ng-animate-ref` attribute) are not removed from the cloned element during the anchor animation. (Previously the `in` animation would accidentally remove the CSS classes of the first element.) Closes angular#11681
Hello !
I'm trying to use the element anchoring feature of ng-animate 1.4 using
ng-animate-ref
.When transitioning to another view, the element is not moving and the animation does not start.
Here is a JSFiddle of the example: https://jsfiddle.net/3eouz22z/3/ and below a gif of the issue.
I tried on Google Chrome 43.0.2357.18 beta (64-bit) on Linux and on Firefox 37.0.1 on Linux.
Thanks for your great work !
The text was updated successfully, but these errors were encountered: