angular.js/test/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(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.
test(ngRepeat): clean up and improve tests 2012-11-26T19:39:10+00:00 Igor Minar 2012-11-23T15:08:47+00:00 6e2c38f54dc012dc919cdd7f7ab9b73dc1e99c66 






test(ngRepeat): add test for issue #1076
2012-11-26T19:38:51+00:00

Igor Minar

2012-11-26T19:17:11+00:00

ff4b3e20c1bcf8f4c76114f5537c8857393c9b2b












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












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







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

Sudhir Jonathan

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

d981c2a3ecfaf572a836c7533ee3a9553aae327d

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($compile): prevent double attr interpolation w/ templateUrl
2012-10-30T02:38:03+00:00

Igor Minar

2012-10-25T07:33:36+00:00

4dbd8452eb93b700c8aaafb7efb97cc20a2c0ff0

This fixes the issue that caused two attr interpolation observers
to be registered for the same attribute as a result of isolate
scope definition with attr (@) property for this attribute.

Duplicate observers would then fight with each other updating the
model.

The issue occured only when this directive was used in a repeater
because that's when we clone the template node which caused the
two observers to point to two different sets of $attr instances.

Closes #1166, #836





This fixes the issue that caused two attr interpolation observers
to be registered for the same attribute as a result of isolate
scope definition with attr (@) property for this attribute.

Duplicate observers would then fight with each other updating the
model.

The issue occured only when this directive was used in a repeater
because that's when we clone the template node which caused the
two observers to point to two different sets of $attr instances.

Closes #1166, #836







fix(currency): Handle not-quite-zero values
2012-10-30T02:37:52+00:00

Braden Shepherdson

2012-10-19T18:29:37+00:00

45a8db9c0814549425542bdb301af9d4a2b50f47

IEEE 754 floating point sometimes results in values that are very small,
rather than zero. One example is 1.0 + 1.07 - 2.07, which returns
4.440892098500626e-16 instead of 0.

This change tweaks the number formatting logic so that an exponential
value with a negative exponent that is larger than the precision+1
returns 0 instead. For example: with precision 2, anything with an
exponent of -4, -5 or more would become 0. 9e-3 = 0.009 = 0.01, but 9e-4
= 0.0009 = 0.001 = 0.00. This detail is unlikely to matter since this
quirk is usually only triggered with values very close to zero.

Closes #1469





IEEE 754 floating point sometimes results in values that are very small,
rather than zero. One example is 1.0 + 1.07 - 2.07, which returns
4.440892098500626e-16 instead of 0.

This change tweaks the number formatting logic so that an exponential
value with a negative exponent that is larger than the precision+1
returns 0 instead. For example: with precision 2, anything with an
exponent of -4, -5 or more would become 0. 9e-3 = 0.009 = 0.01, but 9e-4
= 0.0009 = 0.001 = 0.00. This detail is unlikely to matter since this
quirk is usually only triggered with values very close to zero.

Closes #1469







fix($compile): reference local in isolate scope
2012-09-22T19:00:16+00:00

Vojta Jina

2012-09-13T09:40:00+00:00

cf2c49ed7fbf56df90d3a28fe74e3c866c38aec2

This was really corner case:
Watcher needs to return changed value, to notify that model might have changed and one more $digest cycle needs to be performed.

The watcher, that takes care of reference binding into an isolate scope ("="), did not return changed value, if the change was from the isolate scope to the parent.

If any other watcher returned change, it worked fine, as this change caused re-digest.

Closes #1272





This was really corner case:
Watcher needs to return changed value, to notify that model might have changed and one more $digest cycle needs to be performed.

The watcher, that takes care of reference binding into an isolate scope ("="), did not return changed value, if the change was from the isolate scope to the parent.

If any other watcher returned change, it worked fine, as this change caused re-digest.

Closes #1272