angular.js/src/ng, branch v1.2.14

style: enable jscs requireRightStickedOperators rule

2014-03-01T00:47:21+00:00

docs(forms): generated CSS classes for forms and inputs must have a ng prefix

2014-02-28T19:59:12+00:00

docs(input): update $parsers NgModelController doc

2014-02-28T19:09:30+00:00

Make it clear that the result of the $parsers pipeline is what goes to the model value.

Closes #5708

feat($animate): animate dirty, pristine, valid, invalid for form/fields

2014-02-28T06:01:34+00:00

Add css animations when form or field status change to/from dirty,
pristine, valid or invalid. This works like animation system present
with ngClass, ngShow, etc.

Closes #5378

docs($sce): fix typo

2014-02-27T09:43:26+00:00

docs($compile): fix typo

2014-02-27T09:42:30+00:00

fix($animate): ensure that animateable directives cancel expired leave animations

2014-02-26T19:53:57+00:00

If enter -> leave -> enter -> leave occurs then the first leave animation will
animate alongside the second. This causes the very first DOM node (the view in ngView
for example) to animate at the same time as the most recent DOM node which ends
up being an undesired effect. This fix takes care of this issue.

Closes #5886

docs(*): fix jsdoc type expressions

2014-02-26T11:47:22+00:00

These errors in the docs were preventing some parts of the docs from being
parsed.

revert: fix($location): parse query string when path is empty in hashbang mode

2014-02-26T06:59:31+00:00

This reverts commit cad717b1171affc3d540cea372576c70b0cb2295.

This change causes regressions in existing code and after closer inspection
I realized that it is trying to fix an issue that is should not be considered
a valid issue.

The location service was designed to work against either "hash" part of the
window.location when in the hashbang mode or full url when in the html5 mode.

This change tries to merge the two modes partially, which is not right. One
reason for this is that the search part of window.location can't be modified
while in the hashbang mode (a browser limitation), so with this change part
of the search object should be immutable and read-only which will only cause
more confusion.

Relates to #5964

feat($parse): support trailing commas in object & array literals

2014-02-25T23:38:37+00:00

Per ECMAScript 5.1 specification trailing commas are allowed in object and
array literals. All modern browsers as well as IE>8 support this syntax.
This commit adds support for such syntax to Angular expressions.