angular.js/test, branch v1.2.9 feat($animate): provide support for DOM callbacks 2014-01-14T18:21:28+00:00 Matias Niemelä 2014-01-14T02:51:08+00:00 dde1b2949727c297e214c99960141bfad438d7a4 






feat($animate): use requestAnimationFrame instead of a timeout to issue a reflow
2014-01-14T18:21:19+00:00

Matias Niemelä

2014-01-12T20:49:52+00:00

4ae3184c5915aac9aa00889aa2153c8e84c14966

Closes #4278
Closes #4225





Closes #4278
Closes #4225







fix($animate): ensure the final closing timeout respects staggering animations
2014-01-14T18:20:50+00:00

Matias Niemelä

2014-01-12T04:44:43+00:00

ed53100a0dbc9119d5dfc8b7248845d4f6989df2












chore($animate): remove useless and expired test
2014-01-14T18:20:27+00:00

Matias Niemelä

2014-01-14T01:51:10+00:00

6df598d9f5a52085b90085b41631ef34f3edc386












fix($animate): prevent race conditions for class-based animations when animating on the same CSS class
2014-01-14T18:20:10+00:00

Matias Niemelä

2014-01-06T04:47:18+00:00

4aa9df7a7ae533531dfae1e3eb9646245d6b5ff4

Closes #5588





Closes #5588







fix($animate): correctly detect and handle CSS transition changes during class addition and removal
2014-01-14T18:19:09+00:00

Matias Niemelä

2014-01-02T22:27:13+00:00

7d5d62dafe11620082c79da35958f8014eeb008c

When a CSS class containing transition code is added to an element then an animation should kick off.
ngAnimate doesn't do this. It only respects transition styles that are already present on the element
or on the setup class (but not the addClass animation).





When a CSS class containing transition code is added to an element then an animation should kick off.
ngAnimate doesn't do this. It only respects transition styles that are already present on the element
or on the setup class (but not the addClass animation).







fix($animate): avoid accidentally matching substrings when resolving the presence of className tokens
2014-01-14T18:18:50+00:00

Matias Niemelä

2014-01-02T19:52:49+00:00

524650a40ed20f01571e5466475749874ee67288












fix($http): ensure default headers PUT and POST are different objects
2014-01-14T00:50:15+00:00

Hendrixer

2014-01-11T23:20:54+00:00

e1cfb1957feaf89408bccf48fae6f529e57a82fe

Send PUT and POST through copy() to make sure they are not the same.

Closes #5742
Closes #5747
Closes #5764





Send PUT and POST through copy() to make sure they are not the same.

Closes #5742
Closes #5747
Closes #5764







revert: fix($route): update current route upon $route instantiation
2014-01-13T23:12:17+00:00

Igor Minar

2014-01-13T23:12:17+00:00

308598795af75c33a966ecb3124f4a640d72458d

This reverts commit 2b344dbd20777fb1283b3a5bcf35a6ae8d09469d.

I think I merged this commit prematurely and in addition to that
we found out that it's breaking google apps.

Jen Bourey will provide more info at the original PR #5681





This reverts commit 2b344dbd20777fb1283b3a5bcf35a6ae8d09469d.

I think I merged this commit prematurely and in addition to that
we found out that it's breaking google apps.

Jen Bourey will provide more info at the original PR #5681







fix($rootScope): prevent infinite $digest by checking if asyncQueue is empty when decrementing ttl
2014-01-13T17:53:38+00:00

Noam Lewis

2013-12-31T01:10:23+00:00

2cd09c9f0e7766bcd191662841b7b1ffc3b6dc3f

An infinite $digest loop can be caused by expressions that invoke a promise.
The problem is that $digest does not decrement ttl unless it finds dirty changes;
it should check also if asyncQueue is empty.
Generally the condition for decrementing ttl should be the same as the
condition for terminating the $digest loop.

Fixes #2622





An infinite $digest loop can be caused by expressions that invoke a promise.
The problem is that $digest does not decrement ttl unless it finds dirty changes;
it should check also if asyncQueue is empty.
Generally the condition for decrementing ttl should be the same as the
condition for terminating the $digest loop.

Fixes #2622