| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2013-12-05 | fix($animate): ensure animations work with directives that share a transclusion | Matias Niemelä | |
| Closes #4716 Closes #4871 Closes #5021 Closes #5278 | |||
| 2013-12-04 | fix($animate): ensure ms durations are properly rounded | Matias Niemelä | |
| Closes #5113 Closes #5162 | |||
| 2013-11-25 | fix(ngAnimate): ensure animations are disabled upon bootstrap for structrual ↵ | Matias Niemelä | |
| animations Closes #5130 | |||
| 2013-11-23 | fix($animate): ensure blocked keyframe animations are unblocked before the ↵ | Matias Niemelä | |
| DOM operation Closes #5106 | |||
| 2013-11-21 | fix(ngAnimate): correctly retain and restore existing styles during and ↵ | Peter Deak | |
| after animation Closes #4869 | |||
| 2013-11-21 | fix($animate): ensure keyframe animations are blocked around the reflow | Matias Niemelä | |
| 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 | |||
| 2013-11-21 | fix($animate): ensure transition animations are unblocked before the dom ↵ | Matias Niemelä | |
| 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 | |||
| 2013-11-21 | fix($animate): ensure addClass/removeClass animations do not snap during reflow | Matias Niemelä | |
| Closes #4892 | |||
| 2013-11-20 | fix(ngAnimate): use a fallback CSS property that doesn't break existing styles | Matias Niemelä | |
| 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 | |||
| 2013-11-20 | fix($animate): ensure the DOM operation isn't run twice | Matias Niemelä | |
| 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 | |||
| 2013-11-08 | fix(animateSpec): run digest to enable animations before tests | Pete Bacon Darwin | |
| 2013-11-06 | fix($animate): only apply the fallback property if any transition animations ↵ | Matias Niemelä | |
| are detected | |||
| 2013-11-05 | feat($animate): ensure CSS transitions can work with inherited CSS class ↵ | Matias Niemelä | |
| 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. | |||
| 2013-11-05 | chore(animateSpec): provide meaningful CSS class names in animation tests | Matias Niemelä | |
| 2013-11-05 | fix($animate): avoid hanging animations if the active CSS transition class ↵ | Matias Niemelä | |
| is missing Closes #4732 Closes #4490 | |||
| 2013-11-05 | fix($animate): ensure staggering animations understand multiple delay values | Matias Niemelä | |
| 2013-11-05 | fix($animate): ensure the active class is not applied if cancelled during reflow | Matias Niemelä | |
| Closes #4699 | |||
| 2013-11-05 | chore(ngAnimate): ensure elapsedTime values are in seconds and millseconds | Matias Niemelä | |
| 2013-10-28 | fix($animate): use direct DOM comparison when checking for $rootElement | Matias Niemelä | |
| Closes #4679 | |||
| 2013-10-28 | fix($animate): ensure former nodes are fully cleaned up when a follow-up ↵ | Matias Niemelä | |
| structural animation takes place Closes #4435 | |||
| 2013-10-28 | fix($animate): ensure enable/disable animations work when the document node ↵ | Matias Niemelä | |
| is used Closes #4669 | |||
| 2013-10-28 | feat(ngAnimate): provide support for staggering animations with CSS | Matias Niemelä | |
| 2013-10-24 | fix($animate): skip unnecessary addClass/removeClass animations | Matias Niemelä | |
| 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 | |||
| 2013-10-23 | fix($animate): ensure animations work properly when the $rootElement is ↵ | Matias Niemelä | |
| being animated Closes #4397 Closes #4231 | |||
| 2013-10-23 | fix($animate): only cancel class-based animations if the follow-up class ↵ | Matias Niemelä | |
| contains CSS transition/keyframe animation code Closes #4463 Closes #3784 | |||
| 2013-10-10 | fix($animate): perform internal caching on getComputedStyle to boost the ↵ | Matias Niemelä | |
| performance of CSS3 transitions/animations Closes #4011 Closes #4124 | |||
| 2013-10-10 | fix($animate): ensure structural animations skip all child animations even ↵ | Matias Niemelä | |
| if no animation is present during compile Closes #3215 | |||
| 2013-10-10 | refactor($animate): queue all successive animations to use only one reflow | Matias Niemelä | |
| 2013-10-10 | fix($animate): cancel any ongoing child animations during move and leave ↵ | Matias Niemelä | |
| animations | |||
| 2013-10-10 | fix($animate): ensure elapsedTime always considers delay values | Matias Niemelä | |
| 2013-10-01 | fix($animator): avoid completing the animation asynchronously unless CSS ↵ | Matias Niemelä | |
| transtiions/animations are present Closes #4023 Closes #3940 | |||
| 2013-10-01 | chore($ngAnimate): simplify vendor prefixes handling in tests | Michał Gołębiowski | |
| 2013-09-30 | fix($animate): ensure transition-property is not changed when only keyframe ↵ | Matias Niemelä | |
| animations are in use Closes #3933 | |||
| 2013-09-26 | fix(ngAnimate): ensure that delays are always considered before an animation ↵ | Matias Niemelä | |
| closes Closes #4028 | |||
| 2013-09-06 | fix(ngAnimate): check elapsedTime on current event | Matias Niemelä | |
| onAnimationProgress now checks the event's elapsedTime property before checking the originalEvent.elapsedTime property. Use browserTrigger with elapsedTime parameter to trigger animation events | |||
| 2013-09-05 | refactor($animate): use CSS3 transition/animation events instead of ↵ | Matias Niemelä | |
| $timeouts to track ongoing animations Closes #3629 Closes #3874 | |||
| 2013-09-03 | fix(ngAnimate): ensure that ngClass is always compiled before enter, leave ↵ | Matias Niemelä | |
| and move animations Closes #3727 Closes #3603 | |||
| 2013-09-03 | fix(ngAnimate): cut down on extra $timeout calls | Matias Niemelä | |
| 2013-08-25 | test(docs): disable brittle tests that need to be rewritten | Igor Minar | |
| 2013-08-25 | style(animateSpec): remove ws | Igor Minar | |
| 2013-08-23 | fix($animate): skip ngAnimate animations if the provided element already has ↵ | Matias Niemelä | |
| transitions/durations attached to it Closes #3587 | |||
| 2013-08-23 | fix($animate): only execute a timeout when transitions or keyframe ↵ | Matias Niemelä | |
| 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 | |||
| 2013-08-23 | feat(ngMock): add support for creating dynamic style sheets within test code | Matias Niemelä | |
| 2013-08-09 | fix(ngAnimate): make sure that the class value passed into ↵ | Matias Niemelä | |
| addClass/removeClass is the base class string value | |||
| 2013-08-09 | chore(ngAnimate): fix incomplete animation test | Matias Niemelä | |
| 2013-07-26 | fix($animate): make animation onComplete callbacks async | Matias Niemelä | |
| 2013-07-26 | fix(ngAnimate): $timeout integration and cancel callbacks added | Matias Niemelä | |
| 2013-07-26 | chore($animate): replace show/hide with addClass/removeClass | Matias Niemelä | |
| 2013-07-26 | feat(ngAnimate): complete rewrite of animations | Matias Niemelä | |
| - 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 | |||
 |
index : angular.js | |
| aboutsummaryrefslogtreecommitdiffstats |