angular.js, branch v1.3.0-beta.3 chore(CHANGELOG.md): add changelog for 1.3.0-beta.3 2014-03-21T18:16:35+00:00 Tobias Bosch 2014-03-21T18:16:35+00:00 3f2d7565322a0c8bf72a1ed9da90885a8707161c 






test($rootScope): add assertion to test ensuring that NaN -> NaN does not throw
2014-03-20T21:53:03+00:00

Caitlin Potter

2014-03-20T03:48:47+00:00

6011145cfe83ffec4c0e1616cc9892b3b35a9bb4

https://github.com/angular/angular.js/commit/fb6062fb9d83545730b993e94ac7482ffd43a62c implements a
fix for NaN values causing $watchCollection to throw an infdig error. This change updates the test
by adding an assertion which explains what is actually being tested a bit better, and may also
provide better information in the event that the test ever fails.

Closes #6758





https://github.com/angular/angular.js/commit/fb6062fb9d83545730b993e94ac7482ffd43a62c implements a
fix for NaN values causing $watchCollection to throw an infdig error. This change updates the test
by adding an assertion which explains what is actually being tested a bit better, and may also
provide better information in the event that the test ever fails.

Closes #6758







chore(release): fix angularjs.org cdn script
2014-03-20T21:28:01+00:00

Tobias Bosch

2014-03-20T21:28:01+00:00

b26fc23b068b5de603b535e0ef63cb5deacf0789












fix(version-info): explicitly specify the remote
2014-03-20T20:55:12+00:00

Chirayu Krishnappa

2014-03-14T00:42:43+00:00

0c930a1a86b3e8c14a1ed87c91f074b434895f93

`git ls-remote --tags` assumes that you have a remote set up for your
current branch.  That isn't the case, at least for me, when I'm working
on local branches.  `grunt write` doesn't do the right thing in that
case (`git ls-remote --tags` bails out and the silent: true param makes
this a pain to debug.)  Prefer explicit to implicit.

Closes #6678.





`git ls-remote --tags` assumes that you have a remote set up for your
current branch.  That isn't the case, at least for me, when I'm working
on local branches.  `grunt write` doesn't do the right thing in that
case (`git ls-remote --tags` bails out and the silent: true param makes
this a pain to debug.)  Prefer explicit to implicit.

Closes #6678.







docs(tutorial): correct spelling mistake
2014-03-20T16:27:01+00:00

alexgarrett

2014-03-20T11:57:41+00:00

2f61b2f04539df5a6879a7f0c2db3fe80b91c0d8












docs($document): add a documentation example.
2014-03-20T03:42:21+00:00

Trevor Ewen

2014-03-20T01:06:50+00:00

4d4da556eb2a401ad92323e04c803ff2e77924b0

The $document docs are pretty empty, and this fills them out a bit. The example itself may not be
particularly useful, but it could be improved or removed later. Works for me.

Closes #6757





The $document docs are pretty empty, and this fills them out a bit. The example itself may not be
particularly useful, but it could be improved or removed later. Works for me.

Closes #6757







docs($q): add mention of Antroid 2.x browser
2014-03-19T19:39:32+00:00

thorn0

2014-02-18T09:52:13+00:00

58f5da86645990ef984353418cd1ed83213b111e

The Android 2.x browser is not ES5-compatible in that it does not allow
use of reserved words as property names. This docs fix adds Android to the
note to the `$q` docs which already make it known that string property
notation should be used when using the `finally` method on `$q`.





The Android 2.x browser is not ES5-compatible in that it does not allow
use of reserved words as property names. This docs fix adds Android to the
note to the `$q` docs which already make it known that string property
notation should be used when using the `finally` method on `$q`.







fix($rootScope): ng-repeat can't handle NaN values. #4605
2014-03-19T18:34:15+00:00

Sekib Omazic

2014-02-09T16:58:11+00:00

fb6062fb9d83545730b993e94ac7482ffd43a62c

$watchCollection checks if oldValue !== newValue which does not work for NaN. This was causing
infinite digest errors, since comparing NaN to NaN in $watchCollection would always return false,
indicating that a change was occuring on each loop.

This fix adds a simple check to see if the current value and previous value are both NaN, and
if so, does not count it as a change.

Closes #4605





$watchCollection checks if oldValue !== newValue which does not work for NaN. This was causing
infinite digest errors, since comparing NaN to NaN in $watchCollection would always return false,
indicating that a change was occuring on each loop.

This fix adds a simple check to see if the current value and previous value are both NaN, and
if so, does not count it as a change.

Closes #4605







test(ngMock): workaround issue with negative timestamps
2014-03-19T04:30:29+00:00

Brett Porter

2014-03-18T04:36:00+00:00

0c65f1ae3e86cd3eed078df4e691402d591cc757

In some specific timezones and operating systems, it seems that
getTimezoneOffset() can return an incorrect value for negative timestamps, as
described in #5017. While this isn't something easily fixed in the mock code,
the tests can avoid that particular timeframe by using a positive timestamp.

Closes #5017
Closes #6730





In some specific timezones and operating systems, it seems that
getTimezoneOffset() can return an incorrect value for negative timestamps, as
described in #5017. While this isn't something easily fixed in the mock code,
the tests can avoid that particular timeframe by using a positive timestamp.

Closes #5017
Closes #6730







fix(select): avoid checking option element selected properties in render
2014-03-19T03:18:42+00:00

Jeff Balboni

2014-01-26T21:17:36+00:00

f40f54c6da4a5399fe18a89d068634bb491e9f1a

In Firefox, hovering over an option in an open select menu updates the selected property of option
elements. This means that when a render is triggered by the digest cycle, and the list of options
is being rendered, the selected properties are reset to the values from the model and the option
hovered over changes. This fix changes the code to only use DOM elements' selected properties in a
comparison when a change event has been fired. Otherwise, the internal new and existing option
arrays are used.

Closes #2448
Closes #5994





In Firefox, hovering over an option in an open select menu updates the selected property of option
elements. This means that when a render is triggered by the digest cycle, and the list of options
is being rendered, the selected properties are reset to the values from the model and the option
hovered over changes. This fix changes the code to only use DOM elements' selected properties in a
comparison when a change event has been fired. Otherwise, the internal new and existing option
arrays are used.

Closes #2448
Closes #5994