angular.js/test, branch v1.2.4

fix($compile): update cloned elements if the template arrives after the cloning

2013-12-06T06:16:25+00:00

If an element has a directive whose content is loaded using `templateUrl`,
and the element is cloned using a linking function before the template arrives,
the clone needs to be updated as well.

This also updates `ngIf` and `ngRepeat` to keep the connection to the clone
of a tranclude function, so that they know about the changes a directive with
`templateUrl` does to the element in the future.

Fixes to #4930.

fix(isElement): return boolean value rather than `truthy` value.

2013-12-06T01:14:05+00:00

angular.isElement currently returns a truthy object/function, or false. This
patch aims to correct this behaviour by casting the result of the isElement
expression to a boolean value via double-negation.

Closes #4519
Closes #4534

chore(Scope): short-circuit after dirty-checking last dirty watcher

2013-12-05T23:37:37+00:00

Stop dirty-checking during $digest after the last dirty watcher has been re-checked.

This prevents unneeded re-checking of the remaining watchers (They were already
checked in the previous iteration), bringing a substantial performance improvement
to the average case run time of $digest.

Closes #5272
Closes #5287

fix($animate): ensure animations work with directives that share a transclusion

2013-12-05T15:54:19+00:00

Closes #4716
Closes #4871
Closes #5021
Closes #5278

fix(ngInit): evaluate ngInit before ngInclude

2013-12-05T07:26:56+00:00

The priority of ngInit is adjusted to occur before ngInclude, and after
ngController. This enables ngInit to initiallize values in a controller's
scope, and also to initiallize values before ngInclude executes.

Closes #5167
Closes #5208

fix(input): ensure ngModelWatch() triggers second digest pass when appropriate

2013-12-05T06:49:11+00:00

Due to an earlier change, ngModelWatch() no longer returns a value to the
caller. This means the digest loop has no way to tell if the watch actually
modified anything and so can not schedule another pass.

This means any watches that watch form or model controller changes
(e.g. watches on form.$valid) that are scheduled prior to an ngModelWatch()
will not be able to see any changes made therin.

This commit fixes this behavior by returning the latest evaluated ng-model
value.

Closes #5258
Closes #5282

fix($animate): ensure ms durations are properly rounded

2013-12-05T00:26:40+00:00

Closes #5113
Closes #5162

fix($rootScope): broadcast $destroy event on $rootScope

2013-12-04T23:29:19+00:00

Fixes #5169

fix($rootScope): clear phase if an exception is raised by a watcher

2013-12-04T18:11:29+00:00

Add calls to clearPhase() when an exception is raised by a watcher
while a digest cycle, in order to not be stuck on `$digest` scope phase

fix($compile): ensure isolated local watches' lastValue is always in sync

2013-12-04T17:45:20+00:00

When using two-way binding with isolate scope, under some circumstances
the lastValue variable captured in the parentValueWatch function can get
out of sync.

Specifically, if both the value in the origin scope as well as the value
in the isolate scope get independently updated to the same value within
one digest cycle, the lastValue is never updated. This potentially causes
the watch to make the wrong decision as to which side to update on subsequent
passes.

This fixes things by ensuring lastValue is always set to the last seen
value even if the watch's logic was short circuited because there was no
difference between the values in the original and isolate scopes.

Closes #5182