angular.js/src/ng, branch v1.2.4 fix($compile): update cloned elements if the template arrives after the cloning 2013-12-06T06:16:25+00:00 Tobias Bosch 2013-11-27T03:55:02+00:00 b0972a2e75909e41dbac6e4413ada7df2d51df3a 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. 
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.
chore(Scope): short-circuit after dirty-checking last dirty watcher 2013-12-05T23:37:37+00:00 Karl Seamon 2013-12-04T00:16:08+00:00 d070450cd2b3b3a3aa34b69d3fa1f4cc3be025dd 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 
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(ngInit): evaluate ngInit before ngInclude 2013-12-05T07:26:56+00:00 Caitlin Potter 2013-11-30T02:02:00+00:00 0e50810c53428f4c1f5bfdba9599df54cb7a6c6e 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 
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 Daniel Tabuenca 2013-12-05T00:25:49+00:00 b6d5439343b9801f7f2a009d0de09cba9aa21a1d 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 
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($rootScope): broadcast $destroy event on $rootScope 2013-12-04T23:29:19+00:00 Jeff Cross 2013-12-04T22:33:58+00:00 d802ed1b3680cfc1751777fac465b92ee29944dc Fixes #5169 
Fixes #5169
docs($interpolate): demonstrate a filter in the interpolated expression 2013-12-04T22:36:42+00:00 Sorin Gitlan 2013-11-28T10:14:51+00:00 e8f4305e9d1587512dbef44733fd162caa1cef59 Closes #5186 
Closes #5186
docs(input): remove deprecated isolated scope pitfall 2013-12-04T22:36:41+00:00 Julien Bouquillon 2013-11-27T23:38:47+00:00 1e7675ad4c6dd472755be65fb21c1788afec5856 The 1.2 release fixed the documented pitfall at 909cabd36d779598763cc358979ecd85bb40d4d7 by isolating only the isolated directive's scope. Closes #5179 
The 1.2 release fixed the documented pitfall at 909cabd36d779598763cc358979ecd85bb40d4d7
by isolating only the isolated directive's scope.

Closes #5179
fix($rootScope): clear phase if an exception is raised by a watcher 2013-12-04T18:11:29+00:00 Thomas Guillory 2013-11-06T14:01:10+00:00 d3c486dd6dfa8d5dca32a3e28aa685fb7260c878 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 
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 Daniel Tabuenca 2013-11-28T06:01:22+00:00 2d0f6ccba896fe34141d6d4f59eef6fba580c5c2 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 
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
style(Scope): remove extra ws 2013-12-03T23:44:13+00:00 Igor Minar 2013-12-03T23:39:36+00:00 4a401bbcf3c3e47fec94d33607032ce931d25fdb