angular.js/test/ng, branch v1.2.8

angular.js/test/ng, branch v1.2.8 feat(select): allow multiline ng-options 2014-01-10T17:50:28+00:00 Ajay Roopakalu 2014-01-04T03:15:21+00:00 43a2f3d0bf435e3626cd679caff4281cfb3415bd This patch allows the ng-options value of a <select> element to span multiple lines, which would previously throw an error when used with filters. Closes #5602

This patch allows the ng-options value of a <select> element to span
multiple lines, which would previously throw an error when used with filters.

Closes #5602

fix($http): return responseText on IE8 for requests with responseType set 2014-01-10T10:25:36+00:00 Igor Minar 2014-01-05T07:42:44+00:00 a9cccbe14f1bd9048f5dab4443f58c804d4259a1 Closes #4464 Closes #4738 Closes #5636

Closes #4464
Closes #4738
Closes #5636

revert: fix($location): return '/' for root path in hashbang mode 2014-01-10T07:47:35+00:00 Igor Minar 2014-01-10T07:16:06+00:00 5a4145fe16bb61720843ae938b789e32dbbfdb7d This reverts commit 63cd873fef3207deef30c7a7ed66f4b8f647dc12. The change breaks existing tests of Google apps. The problem is that while we tried to avoid adding #/ to window.location.href unnecessarily we failed doing so. Likely because by setting $path, at some point (during a digest) we try to check if $location changed and we mistake the default '/' with an explicit settign of the path via the `path()` method. This results in us writing the url with '#/' into $browser.url() which updates the window.location by adding "#/" to the url - something we tried to avoid in the first place. I'll reopen PR #5712.

This reverts commit 63cd873fef3207deef30c7a7ed66f4b8f647dc12.

The change breaks existing tests of Google apps. The problem is that
while we tried to avoid adding #/ to window.location.href unnecessarily
we failed doing so. Likely because by setting $path, at some point
(during a digest) we try to check if $location changed and we mistake the
default '/' with an explicit settign of the path via the `path()` method.
This results in us writing the url with '#/' into $browser.url() which updates
the window.location by adding "#/" to the url - something we tried to avoid
in the first place.

I'll reopen PR #5712.

fix($location): return '/' for root path in hashbang mode 2014-01-10T01:35:25+00:00 Caitlin Potter 2014-01-09T19:19:41+00:00 63cd873fef3207deef30c7a7ed66f4b8f647dc12 Before this change, on the root of the application, $location.path() would return the empty string. Following this change, it will always return a root of '/'. Closes #5650 Closes #5712

Before this change, on the root of the application, $location.path() would return
the empty string. Following this change, it will always return a root of '/'.

Closes #5650
Closes #5712

fix($httpBackend): Allow status code 0 from any protocol 2014-01-09T18:10:11+00:00 Rafał Jagoda 2013-12-27T11:55:02+00:00 28fc80bba0107075ab371fd0a7634a38891626b2 Android 4.1 stock browser also returns status code 0 when a template is loaded via `http` and the application is cached using appcache. Fixes #1356. Closes #5547.

Android 4.1 stock browser also returns status code 0 when
a template is loaded via `http` and the application is cached using
appcache.

Fixes #1356.
Closes #5547.

fix($httpBackend): cancelled JSONP requests will not print error in the console 2014-01-08T08:35:19+00:00 Artemy Tregubenko 2014-01-03T15:22:55+00:00 95e1b2d6121b4e26cf87dcf6746a7b8cb4c25e7f When you cancel a JSONP request, angular deletes the callback for it. However the script still executes, and since the callback is now deleted and undefined, the script throws an exception visible in the console. The quick fix for this is not to delete the callback, but replace it with `angular.noop`. Closes #5615 Closes #5616

When you cancel a JSONP request, angular deletes the callback for it. However the script still executes, and since the callback is now deleted and undefined, the script throws an exception visible in the console. The quick fix for this is not to delete the callback, but replace it with `angular.noop`.

Closes #5615
Closes #5616

chore(inputSpec): fixed typo 2014-01-07T00:37:47+00:00 Ben Wiklund 2014-01-06T04:01:33+00:00 eb90672aae0fae1fdcd8b05b14b04f1e6818662b

refactor(filterFilter): simplify code by a ternary op instead of if-else 2014-01-05T08:36:04+00:00 RoyLING 2014-01-05T07:51:04+00:00 e0ce9ed36d9b8c1858e4f928b61d21d7d4c023b8 - use only one IIFE and a ternary op in it, instead of invoking separate IIFEs in if-else (this also completely fixed the same issue closed by PR #3597) - also add a spec to verify usage of '$' property in expression object (e.g. `{$: 'a'}`) Closes #5637

- use only one IIFE and a ternary op in it, instead of invoking separate IIFEs in if-else
(this also completely fixed the same issue closed by PR #3597)
- also add a spec to verify usage of '$' property in expression object (e.g. `{$: 'a'}`)

Closes #5637

fix($parse): fix CSP nested property evaluation, and issue that prevented its tests from failing 2014-01-03T22:33:54+00:00 Brian Nenninger 2014-01-02T05:42:59+00:00 3b1a4fe0c83c7898ecd7261ab4213998ee7be0ec cspSafeGetterFn incorrectly returned undefined if any of its key parameters were undefined. This wasn't caught by the $parse unit tests because of a timing problem where $ParseProvider was reading the CSP flag before the tests manually set it, so the CSP property evaluation tests never ran. Add test that verifies evaluation of nested properties of multiple lengths. Closes #5591 Closes #5592

cspSafeGetterFn incorrectly returned undefined if any of its key parameters were undefined. This
wasn't caught by the $parse unit tests because of a timing problem where $ParseProvider was reading
the CSP flag before the tests manually set it, so the CSP property evaluation tests never ran. Add
test that verifies evaluation of nested properties of multiple lengths.

Closes #5591
Closes #5592

fix($httpBackend): don't delete xhr.onreadystatechange otherwise Safari :-O 2014-01-03T17:51:05+00:00 Igor Minar 2014-01-03T17:23:51+00:00 3d38fff8b4ea2fd60fadef2028ea4dcddfccb1a4