This repository has been 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.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix($animate): use a scheduled timeout in favor of a fallback propert…
…y to close transitions With ngAnimate, CSS transitions, that are not properlty triggered, are forceably closed off by appling a fallback property. The fallback property approach works, however, its styling itself may effect CSS inheritance or cause the element to render improperly. Therefore, its best to stick to using a scheduled timeout to run sometime after the highest animation time has passed. Closes #5255 Closes #5241 Closes #5405
- Loading branch information
Showing
3 changed files
with
128 additions
and
171 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
54637a3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@matsko Not sure if this checkin is the culprit, but your "Rolling out animations with your own directives" example no longer works in 1.2.6+ (but works if I switch the version to 1.2.5). This is the only $animate commit so I'm thinking this could be the cause.
http://plnkr.co/edit/gaoKAVZWeCF5elBdVYjI?p=preview
It works on the first step, but not the subsequent steps (only between step 0 and step 1)
54637a3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@marcfallows looks like 1.2 is failing and 1.3. is fine. I will take a look at it.