This repository was archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27.4k
$animator and ngShow: initial state #2309
Comments
Noticed this as well. Quite an uncomfortable behaviour |
I'm having the same issue. I ended up removing the animations for now. |
+1 Can't use ng-animation with that behavior :( |
We are aware of this and working on a fix where the animation would be disabled for the first render. In the mantime you can work around it by having your own |
Resolved |
Adding class "ng-hide-add-active" to the element forces the final hidden state on start.
|
Thank you @robwalch ! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am using ngShow directive to show some elements on the page, that are initially hidden. As 1.1.4 added animations, I've decided to try to add them to page and used example from documentations.
But as result when initial value is 'false' and document loaded, I see that elements, that should be hidden by ngShow are visible and classes "..-hide-setup", "...-hide-start" are been applied.
This brings to undesired behavior: hidden elements start hiding themselves instead of been hidden initially.
Here is Plunker that illustrate that situation: http://plnkr.co/edit/67Q96KmExV78Kd84tq4g
Is this 'by design' or should be fixed? Now I am checking ngShowDirective and $animator sources to find a solution how to inform $animator that it should skip animation when it is initial value...
The text was updated successfully, but these errors were encountered: