| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2013-08-02 | chore(ngMock): rename $animate.process to $animate.flushNext() | 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 | |||
| 2013-07-15 | fix($animator): ensure animations are always disabled for an element that is ↵ | Matias Niemelä | |
| not attached to the DOM | |||
| 2013-05-08 | chore(ngAnimate): CSS classes X-setup/X-start -> X/X-active | Matias Niemelä | |
| BREAKING CHANGE: css classes foo-setup/foo-start become foo/foo-active The CSS transition classes have changed suffixes. To migrate rename .foo-setup {...} to .foo {...} .foo-start {...} to .foo-active {...} or for type: enter, leave, move, show, hide .foo-type-setup {...} to .foo-type {...} .foo-type-start {...} to .foo-type-active {...} | |||
| 2013-05-08 | feat($sniffer): Add support for supportsAnimations flag for detecting CSS ↵ | Matias Niemelä | |
| Animations browser support | |||
| 2013-04-19 | feat(ngIf): add directive to remove and recreate DOM elements | Oren Avissar | |
| This directive is adapted from ui-if in the AngularUI project and provides a complement to the ngShow/ngHide directives that only change the visibility of the DOM element and ngSwitch which does change the DOM but is more verbose. | |||
