angular.js/css, branch v1.3.0-beta.2 fix($animate): ensure $animate doesn't break natural CSS transitions 2014-02-15T00:30:48+00:00 Matias Niemelä 2014-02-14T09:02:46+00:00 4f84f6b3e4210ae1eb14728a46d43dd961700a0c BREAKING CHANGE: ngClass and {{ class }} will now call the `setClass` animation callback instead of addClass / removeClass when both a addClass/removeClass operation is being executed on the element during the animation. Please include the setClass animation callback as well as addClass and removeClass within your JS animations to work with ngClass and {{ class }} directives. Closes #6019 
BREAKING CHANGE: ngClass and {{ class }} will now call the `setClass`
animation callback instead of addClass / removeClass when both a
addClass/removeClass operation is being executed on the element during the animation.

Please include the setClass animation callback as well as addClass and removeClass within
your JS animations to work with ngClass and {{ class }} directives.

Closes #6019
fix($animate): use a scheduled timeout in favor of a fallback property to close transitions 2013-12-19T17:01:12+00:00 Matias Niemelä 2013-12-14T05:30:48+00:00 54637a335f885110efaa702a3bab29c77644b36c 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 
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
fix(ngAnimate): use a fallback CSS property that doesn't break existing styles 2013-11-21T01:54:07+00:00 Matias Niemelä 2013-11-15T05:09:37+00:00 1d50663b38ba042e8d748ffa6d48cfb5e93cfd7e 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 
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): only apply the fallback property if any transition animations are detected 2013-11-06T07:01:19+00:00 Matias Niemelä 2013-11-06T06:57:34+00:00 9470080762aecca5285d0f5cac4ae01540bbad4c 






fix($animate): avoid hanging animations if the active CSS transition class is missing
2013-11-06T02:45:36+00:00

Matias Niemelä

2013-10-31T21:09:49+00:00

b89584db10b63f346cbfd03f67fb92504e5bf362

Closes #4732
Closes #4490





Closes #4732
Closes #4490







fix(ngShowHide): change the .ng-hide CSS class to use an !important flag
2013-08-03T06:55:53+00:00

Matias Niemelä

2013-07-30T00:32:55+00:00

246c1439b502b06823650505cbe4a3848b6fa5a3












feat(ngAnimate): complete rewrite of animations
2013-07-27T06:49:54+00:00

Matias Niemelä

2013-06-18T17:59:57+00:00

81923f1e41560327f7de6e8fddfda0d2612658f3

- 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





- 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







fix(ngCloak): hide element even when CSS 'display' is set
2013-07-03T05:57:34+00:00

Vineet Kumar

2013-06-26T03:37:56+00:00

3ffddad100e993403d13137387d0685466b46b2b

Previously an element like
<div class="foo ng-cloak">...</div>
would still be annoyingly visible if it matched a CSS rule like
.foo { display: inline-block; }, overriding ng-cloak's display: none.





Previously an element like
<div class="foo ng-cloak">...</div>
would still be annoyingly visible if it matched a CSS rule like
.foo { display: inline-block; }, overriding ng-cloak's display: none.







refactor(directives): connect new compiler
2012-01-25T19:50:37+00:00

Misko Hevery

2011-11-23T05:28:39+00:00

9ee2cdff44e7d496774b340de816344126c457b3

- turn everything into a directive





- turn everything into a directive







refactor(filter): filters are now injectable and services
2011-11-15T04:31:09+00:00

Misko Hevery

2011-11-03T22:59:18+00:00

cb6f832f38b11499a6d1dd2caf14d15e68211635

BREAK:
 - removed CSS support from filters





BREAK:
 - removed CSS support from filters