angular.js/src/ng, branch v1.0.3 fix($location): reset $location.$$replace with every watch call 2012-11-26T22:24:39+00:00 Rado Kirov 2012-09-22T01:57:22+00:00 fc781560a341c804b02c7efd30c6d3010206401c Closes #1111 
Closes #1111
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.
fix(Scope): allow removing a listener during event 2012-11-25T10:41:32+00:00 Vojta Jina 2012-09-25T08:09:26+00:00 ef1874d1f3349844fcd172657cd0a4beac5ffd23 






docs(api): add ngRequired to input/select/textarea directives
2012-11-25T00:19:47+00:00

Dean Sofer

2012-11-09T00:15:50+00:00

55150a669a8496b597267a522955f5cecda7b5d9

Closes #1202





Closes #1202







fix($cacheFactory): return undefined when removing non-existent entry
2012-11-24T20:58:17+00:00

Jeremy Tymes

2012-11-13T12:33:26+00:00

1eb9e22d450aa0b5c2221313e8c83dc5a47e3981

Instead of throwning an exception, remove should return undefined when
cache entry to be removed doesn't exist.

Closes #1497





Instead of throwning an exception, remove should return undefined when
cache entry to be removed doesn't exist.

Closes #1497







docs($q): fix missing bracket in the example
2012-11-22T07:28:49+00:00

Uri Goldshtein

2012-09-12T16:05:26+00:00

1f5bc0a1cd65fb47603f154fb2abfc19bd6daae7












fix($rootScope): workaround for Chrome's memleak
2012-11-14T18:53:29+00:00

Igor Minar

2012-11-14T18:53:29+00:00

1fe666192b0d318b3c907db2119263cd4efa908e

Under certain circumstances chrome fails to GC scopes
because of buggy optimizations and caching. Nulling out
references to (not from!) other scopes helps Chrome to
realize that this object should be GC-ed.

This is really just a workaround as the real problem needs
to be fixed in Chrome.

See discusstion at:
https://github.com/angular/angular.js/issues/1313#issuecomment-10378451

And chrome bug at:
https://code.google.com/p/v8/issues/detail?id=2073

Closes #1313





Under certain circumstances chrome fails to GC scopes
because of buggy optimizations and caching. Nulling out
references to (not from!) other scopes helps Chrome to
realize that this object should be GC-ed.

This is really just a workaround as the real problem needs
to be fixed in Chrome.

See discusstion at:
https://github.com/angular/angular.js/issues/1313#issuecomment-10378451

And chrome bug at:
https://code.google.com/p/v8/issues/detail?id=2073

Closes #1313