angular.js/src, branch v1.2.10

feat($animate): provide support for a close callback

2014-01-24T17:21:29+00:00

Closes #5685
Closes #5053
Closes #4993

docs(ngdoc): ensure module installation docs are accurate

2014-01-23T17:27:30+00:00

The ngMock module is built into a package called angular-mocks, which is
not named consistently and the docs were giving invalid info.

Closes #5810

fix(a): don't preventDefault on click when SVGAElement has an xlink:href attribute

2014-01-22T19:51:47+00:00

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

docs(ngRoute): grammar correction

2014-01-22T19:26:33+00:00

grammar: occurs -> occur

Closes #5937

style($interval): remove ws and replace comma with semicolon

2014-01-22T19:14:59+00:00

docs(ngMock): $log.error property contains messages from $log.error, not $log.log

2014-01-22T16:34:56+00:00

Closes #5932

fix(input): use Chromium's email validation regexp

2014-01-22T02:40:55+00:00

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

docs(select): add callout style for a note

2014-01-22T01:02:50+00:00

docs(select): add object comparison warning

2014-01-22T00:58:41+00:00

fix(ngRoute): pipe preceding route param no longer masks ? or * operator

2014-01-22T00:56:57+00:00

Before this change,

```js
$routeProvider.when('/foo/:bar|?', { ... });
```

would not have the expected effect --- the parameter would not be optional, and
the pipe would not be included in the parameter name.

Following this change, the presence of the pipe operator will typically cause an
exception to be thrown due to the fact that the generated regexp is invalid.

The net result of this change is that ? and * operators will not be masked, and
pipe operators will need to be removed, although it's unexpected that these are
being used anywhere.

Closes #5920