angular.js/css, branch v1.2.8

fix($animate): use a scheduled timeout in favor of a fallback property to close transitions

2013-12-19T17:01:12+00:00

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

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

fix($animate): avoid hanging animations if the active CSS transition class is missing

2013-11-06T02:45:36+00:00

Closes #4732
Closes #4490

fix(ngShowHide): change the .ng-hide CSS class to use an !important flag

2013-08-03T06:55:53+00:00

feat(ngAnimate): complete rewrite of animations

2013-07-27T06:49:54+00:00

- 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

Previously an element like
...
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

- turn everything into a directive

refactor(filter): filters are now injectable and services

2011-11-15T04:31:09+00:00

BREAK:
 - removed CSS support from filters

fix(css): ng:form should always be a block element

2011-10-31T05:26:32+00:00