| Age | Commit message (Collapse) | Author | 
 | 
values to trigger animations
Closes #5357
Closes #5283
 | 
 | 
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
 | 
 | 
jQuery's elem.html('') is way slower than elem.empty(). As clearing
element contents happens quite often in certain scenarios, switching
to using .empty() provides a significant performance boost when using
Angular with jQuery.
Closes #4457
 | 
 | 
Closes #4716
Closes #4871
Closes #5021
Closes #5278
 | 
 | 
Closes #5113
Closes #5162
 | 
 | 
fix the copy/paste typo within $animate.leave method inside of the $animate docs.
 | 
 | 
The example in the section "JavaScript-defined Animations" would not run without the ngAnimate dependency. Also added a missing comma and semicolons.
 | 
 | 
animations
Closes #5130
 | 
 | 
DOM operation
Closes #5106
 | 
 | 
after animation
Closes #4869
 | 
 | 
 | 
 | 
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
 | 
 | 
operation occurs
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
 | 
 | 
Closes #4892
 | 
 | 
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
 | 
 | 
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
 | 
 | 
Line 162: 'defiend' should be 'defined'
Line 225: 'callback function be excuted' should be 'callback function will be executed'.
Closes #5048
 | 
 | 
 | 
 | 
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).
 | 
 | 
 | 
 | 
are detected
 | 
 | 
 | 
 | 
definitions
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.
 | 
 | 
is missing
Closes #4732
Closes #4490
 | 
 | 
 | 
 | 
Closes #4699
 | 
 | 
Closes #4679
 | 
 | 
structural animation takes place
Closes #4435
 | 
 | 
is used
Closes #4669
 | 
 | 
 | 
 | 
Skip addClass animations if the element already contains the class that is being
added to element. Also skip removeClass animations if the element does not contain
the class that is being removed.
Closes #4401
Closes #2332
 | 
 | 
 | 
 | 
being animated
Closes #4397
Closes #4231
 | 
 | 
contains CSS transition/keyframe animation code
Closes #4463
Closes #3784
 | 
 | 
 | 
 | 
 | 
 | 
fix ngAnimate throwing exception in cancelChildAnimations on deletion of
element (ngAnimate's leave decorator) of repeated element when using
ng-include on this element.
Closes #4548
 | 
 | 
This also contains some whitespace corrections by my editor.
 | 
 | 
browser event
Firefox and (sometimes) Opera may not provide a timeStamp value in their event when passed
to the event handler. This may cause animations not to close properly. This fix will automatically
create a timeStamp value for the event in this situation when missing.
Closes #3053
 | 
 | 
Link was set to ngShow and it should be set to ngClass.
 | 
 | 
performance of CSS3 transitions/animations
Closes #4011
Closes #4124
 | 
 | 
if no animation is present during compile
Closes #3215
 | 
 | 
 | 
 | 
animations
 | 
 | 
 | 
 | 
each animation
 | 
 | 
transtiions/animations are present
Closes #4023
Closes #3940
 | 
 | 
To avoid code duplication, use single variables for keeping
properties/events names to use. Also, fix some errors that have
happened after the rewrite from moment ago.
 | 
 | 
animations are in use
Closes #3933
 | 
 | 
closes
Closes #4028
 |