angular.js/test/ng, branch v1.2.0-rc.2 fix(ngAnimate): ensure that ngClass is always compiled before enter, leave and move animations 2013-09-04T00:06:49+00:00 Matias Niemelä 2013-08-28T23:32:20+00:00 36ad40b18cfdd0690411a5169aa94e222946b5cf Closes #3727 Closes #3603 
Closes #3727
Closes #3603
chore($rootScope): provide support to execute a function after the digest cycle is complete 2013-09-04T00:06:49+00:00 Matias Niemelä 2013-08-14T00:51:03+00:00 4e15c4fb47e93c1f6619a09125bc9a350e39b113 






fix(ngAnimate): cut down on extra $timeout calls
2013-09-04T00:06:49+00:00

Matias Niemelä

2013-08-28T23:18:33+00:00

4382df03fa1962aed027742c1b463406c40653c9












fix($http): allow empty responses to be cached
2013-09-02T09:47:51+00:00

jankuca

2013-08-30T01:52:30+00:00

8e48c4ff6abf7083a04cf20312d2b106f4ba5b2c

Closes #3809





Closes #3809







fix(core): parse IE11 UA string correctly
2013-08-29T23:07:49+00:00

Chirayu Krishnappa

2013-08-27T00:26:08+00:00

427ee93f11d0ef64b8844f9b43b2a0f21f2be2cb

It's great that IE11 wants to be compatible enough that it doesn't want
to be special cased and treated differently.

However, as long as one has to have a different code path for IE than
for the other supported browsers, we still need to detect and special
case it.  For instance, our URL parsing code still needs the same
workaround the we used for IE10.  We still see the same Access denied /
TypeError exceptions when setting certain values.  FYI, Angular doesn't
generally blindly test for IE – we also check the version number.

Thanks to modern.ie for the free IE11 test VM.

Closes #3682





It's great that IE11 wants to be compatible enough that it doesn't want
to be special cased and treated differently.

However, as long as one has to have a different code path for IE than
for the other supported browsers, we still need to detect and special
case it.  For instance, our URL parsing code still needs the same
workaround the we used for IE10.  We still see the same Access denied /
TypeError exceptions when setting certain values.  FYI, Angular doesn't
generally blindly test for IE – we also check the version number.

Thanks to modern.ie for the free IE11 test VM.

Closes #3682







test(Scope): fix tests after reverting commits
2013-08-28T05:36:23+00:00

Igor Minar

2013-08-28T05:36:23+00:00

e86de0db56e156d6c603584c440026effaf19b82

Making assertions on state (rather than interactions) is better anyway.





Making assertions on state (rather than interactions) is better anyway.







revert: feat(mocks): make $timeout#flush throw an exception when empty
2013-08-28T00:23:36+00:00

Igor Minar

2013-08-28T00:20:30+00:00

4114f9c21bec5a396e59954dfc42d2c96527ac3d

This reverts commit cbf06a5d64aba537f0e2679a194d3998d8365493.

This turned out to be a bad idea because it allow us to fast-forward
the wall clock time (see previous commit).





This reverts commit cbf06a5d64aba537f0e2679a194d3998d8365493.

This turned out to be a bad idea because it allow us to fast-forward
the wall clock time (see previous commit).







feat(Scope): async auto-flush $evalAsync queue when outside of $digest
2013-08-26T16:06:25+00:00

Igor Minar

2013-08-22T09:08:41+00:00

6b91aa0a18098100e5f50ea911ee135b50680d67

This change causes a new $digest to be scheduled in the next tick if
a task was was sent to the $evalAsync queue from outside of a $digest
or an $apply.

While this mode of operation is not common for most of the user code,
this change means that $q promises that utilze $evalAsync queue to
guarantee asynchronicity of promise apis will now also resolve outside
of a $digest, which turned out to be a big pain point for some developers.

The implementation ensures that we don't do more work than needed and
that we coalese as much work as possible into a single $digest.

The use of $browser instead of setTimeout ensures that we can mock out
and control the scheduling of "auto-flush", which should in theory
allow all of the existing code and tests to work without negative
side-effects.

Closes #3539
Closes #2438





This change causes a new $digest to be scheduled in the next tick if
a task was was sent to the $evalAsync queue from outside of a $digest
or an $apply.

While this mode of operation is not common for most of the user code,
this change means that $q promises that utilze $evalAsync queue to
guarantee asynchronicity of promise apis will now also resolve outside
of a $digest, which turned out to be a big pain point for some developers.

The implementation ensures that we don't do more work than needed and
that we coalese as much work as possible into a single $digest.

The use of $browser instead of setTimeout ensures that we can mock out
and control the scheduling of "auto-flush", which should in theory
allow all of the existing code and tests to work without negative
side-effects.

Closes #3539
Closes #2438







feat(mocks): make $timeout#flush throw an exception when empty
2013-08-25T21:46:54+00:00

Igor Minar

2013-08-24T21:18:47+00:00

cbf06a5d64aba537f0e2679a194d3998d8365493

When calling $timeout.flush with or without a delay an exception should
be thrown if there is nothing to be flushed.

This prevents tests from flushing stuff unnecessarily.

BREAKING CHANGE: calling $timeout.flush(delay) when there is no task to be flushed
within the delay throws an exception now.

Please adjust the delay or remove the flush call from your tests as the exception
is a signed of a programming error.





When calling $timeout.flush with or without a delay an exception should
be thrown if there is nothing to be flushed.

This prevents tests from flushing stuff unnecessarily.

BREAKING CHANGE: calling $timeout.flush(delay) when there is no task to be flushed
within the delay throws an exception now.

Please adjust the delay or remove the flush call from your tests as the exception
is a signed of a programming error.







fix($q): reject should catch & forward exceptions thrown in errback
2013-08-24T19:49:46+00:00

Igor Minar

2013-08-22T05:57:48+00:00

5d9f42050a11015adbd5dc4dde73818919e93a99