angular.js/src/ng/directive, branch v1.1.1 fix(ngClassOdd/ngClassEven): support shrinking/reordering in repeaters 2012-11-26T19:36:53+00:00 Igor Minar 2012-11-23T21:46:58+00:00 d859dcecea654d1d858cd756c6efb8435a453197 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-26T19:36:53+00:00 Igor Minar 2012-11-23T21:43:30+00:00 1b17dfa693c36607ea86c7129a8612f7771c2f22 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-26T19:36:53+00:00 Igor Minar 2012-11-23T21:40:01+00:00 e6d9bea4f3b2eb28851298d3dc3a30d46062d58a 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:31:54+00:00 Igor Minar 2012-11-26T19:25:38+00:00 d644dcfa52cba0cee3c6fa8d03e1654cdb654e53 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.
feat(form): add ability to reset a form to pristine state 2012-11-26T15:44:34+00:00 Pawel Kozlowski 2012-07-07T17:02:04+00:00 733a97adf87bf8f7ec6be22b37c4676cf7b5fc2b Retting a form to pristine state will cause all of the nested form and form controls to be recursively reset as well. Closes #856 
Retting a form to pristine state will cause all of the nested
form and form controls to be recursively reset as well.

Closes #856
docs(api): add ngRequired to input/select/textarea directives 2012-11-25T00:18:10+00:00 Dean Sofer 2012-11-09T00:15:50+00:00 c8fd7fd0e2c77cc3d22382367ed5a1537383bee6 Closes #1202 
Closes #1202
docs(ngList): fix typo 2012-11-11T10:24:59+00:00 Josh Adams 2012-11-05T20:42:54+00:00 ffa6c5195fdc1c9a7d27e2cd20ac3f2e0ef46f74 






docs(ngHide): Fix typo and make it more in line with ngShow
2012-11-11T09:36:28+00:00

Christian Vuerings

2012-11-09T13:44:00+00:00

f3e053cb6fec8279e09330481ba8906e185f94c6












fix(select): select option with a label of 0 is not shown
2012-10-31T22:03:13+00:00

Sudhir Jonathan

2012-10-21T07:27:27+00:00

b3cae4f457f1688346bbd0b08cccc9c504f83406

Bug caused by the use of the `||` operator to replace all non-truthy
values with an empty string. Changed to replace only `undefined` values.

Closes #1401





Bug caused by the use of the `||` operator to replace all non-truthy
values with an empty string. Changed to replace only `undefined` values.

Closes #1401







fix(a): prevent Opera from incorrectly navigating on link click
2012-09-06T23:06:27+00:00

sgtpep

2012-07-26T21:26:46+00:00

c81d8176cc55cd15acae05259ead73f90a01f0b7

we handle the navigation by ourselves, so we need to prevent the default action.

Opera ignores event.preventDefault() call so we must return false.





we handle the navigation by ourselves, so we need to prevent the default action.

Opera ignores event.preventDefault() call so we must return false.