-
Notifications
You must be signed in to change notification settings - Fork 678
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes all instances of $animate.enter() to follow angular 1.3.x semantics without breaking 1.2.x #170
Conversation
…antics without breaking 1.2.x
Nice! Thanks! |
Changes all instances of $animate.enter() to follow angular 1.3.x semantics without breaking 1.2.x
@chieffancypants @assisrafael this does not take into account if parent does not have children. In these situations, the bar is never appended. According to angular's
If parent doesn't have children, the after element will be defined but empty. |
@joaovieira what do you suggest? |
@chieffancypants I had another look... Although the migration document suggests to use Also, if there's no children in the parent element: Because of this, using simply:
Will do. If the lastChild is null, it remains null until the end and the bar is prepended in the parent, if lastChild exists the bar is prepended after it. But if it's [] it does nothing :) I can create the PR with the test case if needed. |
Sorry, seems like that won't work with the default $animate (funny that the ngAnimateMock only delegates to the default and doesn't really behave like the real implementation...). I'd then suggest doing the same check ngAnimate does?
|
I think you should start by writing a test case that breaks. It will help in your search for the proper solution. |
PR #218 |
According to the angular migration guide the $animate.enter() method behavior has changed. This change causes flickering for some Angular 1.3.x apps. I was not able to isolate a small scenario.