angular.js/src/ngAnimate, branch v1.2.0

fix($animate): don't force animations to be enabled

2013-11-08T09:03:17+00:00

The way that enabling of animations was set up, made it impossible to inject a
module into the bootstrap to disable animations for things like end 2 end tests.
Now animations are temporarily blocked by setting the animation state to RUNNING
during bootstrap, which allows the developer to permanently disable at any point
by calling $animate.enabled(false).

refactor($animate): speed up animationsDisabled check

2013-11-08T09:03:17+00:00

fix($animate): only apply the fallback property if any transition animations are detected

2013-11-06T07:01:19+00:00

chore(docs): update $animate and ngAnimate docs

2013-11-06T05:21:17+00:00

feat($animate): ensure CSS transitions can work with inherited CSS class definitions

2013-11-06T05:15:59+00:00

BREAKING CHANGE

ngAnimate addClass / removeClass animations are now applied right away. This means
that as soon as the animation starts the class will be added (addClass) or removed
(removeClass) to the element being animated instead of after the -add-active /
-remove-active animations are completed. This allows for animations outside of
ngAnimate to not conflict with $animate.

This commit introduces beforeAddClass and beforeRemoveClass animation event functions and
executes any addClass and removeClass event functions AFTER the class has been added or
removed (this is opposite functionality of how ngAnimate used to work when performing
JS-enabled animations addClass / removeClass animations). If your animation code relies on
any animations being performed prior to the class change then simply use the new
beforeAddClass and beforeRemoveClass animation event functions.

Finally, when animating show and hide animations using CSS transitions or keyframe animations,
ng-hide-remove doesn't require `display:block!important` for ng-hide-add anymore.

fix($animate): avoid hanging animations if the active CSS transition class is missing

2013-11-06T02:45:36+00:00

Closes #4732
Closes #4490

fix($animate): ensure staggering animations understand multiple delay values

2013-11-06T02:44:25+00:00

fix($animate): ensure the active class is not applied if cancelled during reflow

2013-11-06T02:44:02+00:00

Closes #4699

fix($animate): use direct DOM comparison when checking for $rootElement

2013-10-29T05:47:47+00:00

Closes #4679

fix($animate): ensure former nodes are fully cleaned up when a follow-up structural animation takes place

2013-10-29T04:26:35+00:00

Closes #4435