| Age | Commit message (Collapse) | Author |
|
|
|
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
|
|
onAnimationProgress now checks the event's elapsedTime property before
checking the originalEvent.elapsedTime property.
Use browserTrigger with elapsedTime parameter to trigger animation events
|
|
$timeouts to track ongoing animations
Closes #3629
Closes #3874
|
|
and move animations
Closes #3727
Closes #3603
|
|
|
|
transitions/durations attached to it
Closes #3587
|
|
animations are used
ngAnimate causes a 1ms flicker on the screen when no CSS animations are present on the element.
The solution is to change $animate to only use $timeouts when a duration is found on the element
before the transition/keyframe animation takes over.
Closes #3613
|
|
Currently, the documentation does a bad job of explaining the distinction between the services that it provides,
and the module itself. Furthermore, the instructions for using optional modules are inconsistent or missing.
This commit addresses the problem by ading a new `{@installModule foo}` annotation to the docs generator that
inlines the appropriate instructions based on the name of the module.
|
|
addClass/removeClass is the base class string value
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
BREAKING CHANGE: previously ngInclude only updated its content, after this change
ngInclude will recreate itself every time a new content is included. This ensures
that a single rootElement for all the included contents always exists, which makes
definition of css styles for animations much easier.
|
|
|
|
- ngAnimate directive is gone and was replaced with class based animations/transitions
- support for triggering animations on css class additions and removals
- done callback was added to all animation apis
- $animation and $animator where merged into a single $animate service with api:
- $animate.enter(element, parent, after, done);
- $animate.leave(element, done);
- $animate.move(element, parent, after, done);
- $animate.addClass(element, className, done);
- $animate.removeClass(element, className, done);
BREAKING CHANGE: too many things changed, we'll write up a separate doc with migration instructions
|