angular.js/test/ng, branch v1.2.10 fix(a): don't preventDefault on click when SVGAElement has an xlink:href attribute 2014-01-22T19:51:47+00:00 Caitlin Potter 2014-01-20T16:21:50+00:00 e0209169bf1463465ad07484421620748a4d3908 Before this change, an SVGAElement with an xlink:href attribute and no href or name attribute which was compiled by the angular HTML compiler would never be clickable, due to the htmlAnchorDirective calling event.preventDefault() due to the missing href attribute. This change corrects this behaviour by also testing the xlink:href attribute if the element in question is determined to be an SVG anchor tag (with the href property having type SVGAnimatedString) Closes #5896 Closes #5897 
Before this change, an SVGAElement with an xlink:href attribute and no href or name attribute which
was compiled by the angular HTML compiler would never be clickable, due to the htmlAnchorDirective
calling event.preventDefault() due to the missing href attribute.

This change corrects this behaviour by also testing the xlink:href attribute if the element in
question is determined to be an SVG anchor tag (with the href property having type SVGAnimatedString)

Closes #5896
Closes #5897
fix(input): use Chromium's email validation regexp 2014-01-22T02:40:55+00:00 Caitlin Potter 2014-01-22T02:19:31+00:00 79e519fedaec54390a8bdacfb1926bfce57a1eb6 This change uses the regexp from Chromium/Blink to validate emails, and corrects an error in the validation engine, which previously considered an invalid email to be valid. Additionally, the regexp was invalidating emails with capital letters, however this is not the behaviour recomended in the spec, or implemented in Chromium. Closes #5899 Closes #5924 
This change uses the regexp from Chromium/Blink to validate emails, and corrects
an error in the validation engine, which previously considered an invalid email
to be valid. Additionally, the regexp was invalidating emails with capital
letters, however this is not the behaviour recomended in the spec, or implemented
in Chromium.

Closes #5899
Closes #5924
fix($parse): do not use locals to resolve object properties 2014-01-22T00:27:04+00:00 Lucas Galfasó 2014-01-17T17:59:49+00:00 f09b6aa5b58c090e3b8f8811fb7735e38d4b7623 Do not use the locals when performing a field access in an angular expression. Closes #5838 Closes #5862 
Do not use the locals when performing a field access in an angular expression.

Closes #5838
Closes #5862
fix($http): ensure default headers PUT and POST are different objects 2014-01-14T00:50:15+00:00 Hendrixer 2014-01-11T23:20:54+00:00 e1cfb1957feaf89408bccf48fae6f529e57a82fe Send PUT and POST through copy() to make sure they are not the same. Closes #5742 Closes #5747 Closes #5764 
Send PUT and POST through copy() to make sure they are not the same.

Closes #5742
Closes #5747
Closes #5764
fix($rootScope): prevent infinite $digest by checking if asyncQueue is empty when decrementing ttl 2014-01-13T17:53:38+00:00 Noam Lewis 2013-12-31T01:10:23+00:00 2cd09c9f0e7766bcd191662841b7b1ffc3b6dc3f An infinite $digest loop can be caused by expressions that invoke a promise. The problem is that $digest does not decrement ttl unless it finds dirty changes; it should check also if asyncQueue is empty. Generally the condition for decrementing ttl should be the same as the condition for terminating the $digest loop. Fixes #2622 
An infinite $digest loop can be caused by expressions that invoke a promise.
The problem is that $digest does not decrement ttl unless it finds dirty changes;
it should check also if asyncQueue is empty.
Generally the condition for decrementing ttl should be the same as the
condition for terminating the $digest loop.

Fixes #2622
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.