angular.js/src/ng/directive, branch v1.0.4 fix(ngSwitch): don't leak when destroyed while not attached 2013-01-18T08:03:42+00:00 danilsomsikov 2013-01-11T17:21:13+00:00 89303fd2dccb780bea594b16b8ec85d9f3bd8f92 The leak can occur when ngSwich is used inside ngRepeat or any other directive which is destroyed while its transcluded content (which includes ngSwitch) is not attached to the DOM. Refactor ngSwitch to use controller instead of storing data on compile node. This means that we don't need to clean up the jq data cache. Controller reference is released when the linking fn is released. Closes #1621 
The leak can occur when ngSwich is used inside ngRepeat or any other
directive which is destroyed while its transcluded content (which
includes ngSwitch) is not attached to the DOM.

Refactor ngSwitch to use controller instead of storing data on compile
node. This means that we don't need to clean up the jq data cache.
Controller reference is released when the linking fn is released.

Closes #1621
fix(ngRepeat): correctly apply $last if repeating over object 2013-01-17T08:25:07+00:00 Pete Bacon Darwin 2013-01-11T12:47:38+00:00 ed2fd2d0caad4e4b45f79bb39fd2a8b03fea8faa If the $last property is calculated from the original collectionLength on an object and properties starting with $ were filtered out, then $last is never applied and $middle is applied erroniously. Closes #1789 
If the $last property is calculated from the original collectionLength
on an object and properties starting with $ were filtered out, then $last
is never applied and $middle is applied erroniously.

Closes #1789
revert: fix(a): prevent Opera from incorrectly navigating on link click 2013-01-08T19:51:17+00:00 Igor Minar 2013-01-08T19:47:22+00:00 4cda02860949cdd090923bca52916cc5c4ecac9a This reverts commit c81d8176cc55cd15acae05259ead73f90a01f0b7. This commit causes several issues (#1651, #1674, #1662) and doesn't even contain a test that proves that anything on Opera got actually fixed. If the original Opera resurfaces, we'll fix it properly. 
This reverts commit c81d8176cc55cd15acae05259ead73f90a01f0b7.

This commit causes several issues (#1651, #1674, #1662) and doesn't even
contain a test that proves that anything on Opera got actually fixed.

If the original Opera resurfaces, we'll fix it properly.
docs(form): minor form doc and example fixes 2013-01-04T16:25:24+00:00 Jonathan Card 2012-12-16T21:32:19+00:00 23cd40a8ec18d1dd947c8cd5d0fb0be68c1bac9c Form documentation fixes: - Fix broken form example in docs - A few small other corrections in form docs. 
Form documentation fixes:
- Fix broken form example in docs
- A few small other corrections in form docs.
docs(ngView): fix code example (change template to templateUrl) 2012-12-18T16:56:04+00:00 Pawel Kozlowski 2012-12-17T22:18:12+00:00 1104c7d75bb095f608854ea583e7773db986a031 Closes #1715 
Closes #1715
fix(select): support optgroup + select[multiple] combo 2012-12-05T01:21:31+00:00 _pants 2012-11-29T16:46:51+00:00 54c0d464b0f34f9bfd076883a6a78cf5925bd975 Closes #1553 
Closes #1553
fix(ngClassOdd/ngClassEven): support shrinking/reordering in repeaters 2012-11-26T20:33:45+00:00 Igor Minar 2012-11-23T21:46:58+00:00 6f18adedef60ddb972a446046270f98c4ac18bb7 We need to watch $index in addition to cssClasses because only then we can correctly respond to shrinking or reordered repeaters. Closes #1076 
We need to watch $index in addition to cssClasses because only then
we can correctly respond to shrinking or reordered repeaters.

Closes #1076
fix(ngRepeat): support mostly-stable repeating for primitives 2012-11-26T20:33:45+00:00 Igor Minar 2012-11-23T21:43:30+00:00 cde2f1a868ffacdc592803358130587fd73aca7b I'm reverting changes that were originally done to ngRepeat to fix #933, because these are now not necessary after the previous changes to keep ngModel always synced with the DOM. 
I'm reverting changes that were originally done to ngRepeat to fix #933,
because these are now not necessary after the previous changes to keep
ngModel always synced with the DOM.
fix(ngModel): sync ngModel state with scope state 2012-11-26T20:33:45+00:00 Igor Minar 2012-11-23T21:40:01+00:00 6a831495dedc81e995bba276084eb3b23643557a In cases when we reuse elements in a repeater but associate them with a new scope (see #933 - repeating over array of primitives) it's possible for the internal ngModel state and the scope state to get out of sync. This change ensure that the two are always sync-ed up even in cases where we reassociate an element with a different (but similar) scope. In the case of repeating over array of primitives it's still possible to run into issue if we iterate over primitives and use form controls or similar widgets without ngModel - oh well, we'd likely need a special repeater for primitives to deal with this properly, even then there might be cornercases. Closes #933 
In cases when we reuse elements in a repeater but associate
them with a new scope (see #933 - repeating over array of
primitives) it's possible for the internal ngModel state and
the scope state to get out of sync. This change ensure that
the two are always sync-ed up even in cases where we
reassociate an element with a different (but similar) scope.

In the case of repeating over array of primitives it's still
possible to run into issue if we iterate over primitives and
use form controls or similar widgets without ngModel - oh well,
we'd likely need a special repeater for primitives to deal
with this properly, even then there might be cornercases.

Closes #933
fix(ngRepeat): attempt to simplify and improve existing fix for #933 2012-11-26T19:39:00+00:00 Igor Minar 2012-11-26T19:25:38+00:00 00e7e3141819e14ced3279fa5dfb8eba4ff89e5f I'm keeping this in for future reference. The issue with this solution is that if we shift() the first item in the array, the whole repeater DOM will be rebuilt from scratch, we need to do better than that. 
I'm keeping this in for future reference. The issue with this solution
is that if we shift() the first item in the array, the whole repeater
DOM will be rebuilt from scratch, we need to do better than that.