This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
Animation is broken when animated content is wrapped in a bootstrap 3 .container #5405
Comments
|
This should be fixed with: #5403 |
matsko
added a commit
to matsko/angular.js
that referenced
this issue
Dec 17, 2013
…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 angular#5255 Closes angular#5241 Closes angular#5405
matsko
added a commit
to matsko/angular.js
that referenced
this issue
Dec 19, 2013
…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 angular#5255 Closes angular#5241 Closes angular#5405
jamesdaily
pushed a commit
to jamesdaily/angular.js
that referenced
this issue
Jan 27, 2014
…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 angular#5255 Closes angular#5241 Closes angular#5405
jamesdaily
pushed a commit
to jamesdaily/angular.js
that referenced
this issue
Jan 27, 2014
…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 angular#5255 Closes angular#5241 Closes angular#5405
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
http://jsfiddle.net/vBnv8/2/
Despite the fact that only opacity is animated, the animated content wobbles and shakes during the animation.
FF 24 and 25, Google Chrome 31.
The regression was introduced by commit 7067a8f (fix($animate): ensure the DOM operation isn't run twice)
The text was updated successfully, but these errors were encountered: