angular.js/test/ngRoute, branch g3_v1_2

fix($animate): ensure that animateable directives cancel expired leave animations

2014-02-26T19:53:57+00:00

If enter -> leave -> enter -> leave occurs then the first leave animation will
animate alongside the second. This causes the very first DOM node (the view in ngView
for example) to animate at the same time as the most recent DOM node which ends
up being an undesired effect. This fix takes care of this issue.

Closes #5886

perf($animate): use rAF instead of timeouts to issue animation callbacks

2014-02-25T02:23:18+00:00

style: remove ws and enfore no-trailing-ws jscs rule

2014-02-18T18:44:48+00:00

fix($animate): ensure $animate doesn't break natural CSS transitions

2014-02-15T00:30:48+00:00

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(mocks): rename mock.animate to ngAnimateMock and ensure it contains all test helper code for ngAnimate

2014-02-06T06:22:14+00:00

Closes #5822
Closes #5917

fix(mocks): remove usage of $animate.flushNext in favour of queing

2014-02-06T06:21:41+00:00

The flushNext method of testing is difficult and highly coupled with the behavior
of ngAnimate's $animate workflow. It is much better instead to just queue all
$animate animation calls into a queue collection which is available on the $animate
service when mock.animate is included as a module within test code.

revert: fix($route): update current route upon $route instantiation

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

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($route): update current route upon $route instantiation

2014-01-11T07:42:36+00:00

This fixes cases where the first ngView is loaded in a template asynchronously (such as through ngInclude), as the service will miss the first  event otherwise.

Closes #4957

fix(ngRoute): instantiate controller when template is empty

2013-12-28T06:45:46+00:00

Before this change, $route controllers are not instantiated if the template is falsy, which includes
the empty string. This change tests if the template is not undefined, rather than just falsy, in
order to ensure that templates are instantiated even when the template is empty, which people may
have some reason to do.

This "bug" was reported in http://robb.weblaws.org/2013/06/21/angularjs-vs-emberjs/, as a "gotcha"
for AngularJS / ngRoute.

Closes #5550

fix(ngView): Add template to DOM before linking other directives

2013-12-13T01:18:44+00:00

The template needs to be added to the DOM before
other directives at the same element as `ngView` are linked.

Related to #5247.