angular.js/src/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

chore($animate): remove unnecessary reflective dereferencing

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

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

docs(ngAnimate): fixed two small typos

2013-11-20T14:32:30+00:00

Line 162: 'defiend' should be 'defined'
Line 225: 'callback function be excuted' should be 'callback function will be executed'.

Closes #5048

docs($animate): update the docs explaining enable/disable for specific elements

2013-11-19T22:50:24+00:00

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).