angular.js/test/ngAnimate, branch v1.2.2

fix(ngAnimate): correctly retain and restore existing styles during and after animation

2013-11-22T04:37:01+00:00

Closes #4869

fix($animate): ensure keyframe animations are blocked around the reflow

2013-11-22T01:48:15+00:00

Keyframe animations trigger on the first CSS class and not the second.
This may cause a slight flicker during a stagger animation since the
animation has already started before the stagger delay is considered.
This fix ensures that the animation is blocked until the active animation
starts which allows for staggering animations to take over properly.

Closes #5018

fix($animate): ensure transition animations are unblocked before the dom operation occurs

2013-11-22T01:48:07+00:00

Transitions are blocked when the base CSS class is added at the start of the animation. This
causes an issue if the followup CSS class contains animatable-styles. Now, once the animation
active state is triggered (when the animation CSS dom operation occurs) the animation itself
will always trigger an animate without a quick jump.

Closes #5014
Closes #4265

fix($animate): ensure addClass/removeClass animations do not snap during reflow

2013-11-22T01:47:55+00:00

Closes #4892

fix(ngAnimate): use a fallback CSS property that doesn't break existing styles

2013-11-21T01:54:07+00:00

The clip property seems to remove the box-shadow property when an absolute
positioned animation is ongoing. This fix changes the property to be border-spacing
which is also very underused. The border-spacing CSS property is only visible
when border-collapse is set to separate.

Closes #4902
Closes #5030

fix($animate): ensure the DOM operation isn't run twice

2013-11-20T22:08:03+00:00

Depending on the animations placed on ngClass, the DOM operation may
run twice causing a race condition between addClass and removeClass.
Depending on what classes are removed and added via $compile this may
cause all CSS classes to be removed accidentally from the element
being animated.

Closes #4949

fix(animateSpec): run digest to enable animations before tests

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

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

2013-11-06T07:01:19+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.

chore(animateSpec): provide meaningful CSS class names in animation tests

2013-11-06T02:46:07+00:00