angular.js/test/ng/directive, branch v1.2.13 fix($animate): ensure $animate doesn't break natural CSS transitions 2014-02-15T00:30:48+00:00 Matias Niemelä 2014-02-14T09:02:46+00:00 4f84f6b3e4210ae1eb14728a46d43dd961700a0c BREAKING CHANGE: ngClass and {{ class }} will now call the `setClass` animation callback instead of addClass / removeClass when both a addClass/removeClass operation is being executed on the element during the animation. Please include the setClass animation callback as well as addClass and removeClass within your JS animations to work with ngClass and {{ class }} directives. Closes #6019 
BREAKING CHANGE: ngClass and {{ class }} will now call the `setClass`
animation callback instead of addClass / removeClass when both a
addClass/removeClass operation is being executed on the element during the animation.

Please include the setClass animation callback as well as addClass and removeClass within
your JS animations to work with ngClass and {{ class }} directives.

Closes #6019
fix(input): setViewValue on compositionend 2014-02-13T01:28:13+00:00 Caitlin Potter 2013-12-16T18:06:16+00:00 2b7302713674506fdbcdc396c38f18dcb90dee8c Because of a4e6d962, model is not updated on input/change between the compositionstart and compositionend events. Unfortunately, the compositionend event does not always happen prior to an input/change event. This changeset calls the listener function to update the model after a compositionend event is received. Closes #6058 Closes #5433 
Because of a4e6d962, model is not updated on input/change between the
compositionstart and compositionend events. Unfortunately, the compositionend
event does not always happen prior to an input/change event.

This changeset calls the listener function to update the model after a
compositionend event is received.

Closes #6058
Closes #5433
fix(mocks): rename mock.animate to ngAnimateMock and ensure it contains all test helper code for ngAnimate 2014-02-06T06:22:14+00:00 Matias Niemelä 2014-01-23T00:28:42+00:00 4224cd5182bc93e4a210f75e0a4e4de7f3c544e8 Closes #5822 Closes #5917 
Closes #5822
Closes #5917
fix(mocks): remove usage of $animate.flushNext in favour of queing 2014-02-06T06:21:41+00:00 Matias Niemelä 2014-01-23T00:21:05+00:00 906fdad0f95465842e336e057ea97d0633712189 The flushNext method of testing is difficult and highly coupled with the behavior of ngAnimate's $animate workflow. It is much better instead to just queue all $animate animation calls into a queue collection which is available on the $animate service when mock.animate is included as a module within test code. 
The flushNext method of testing is difficult and highly coupled with the behavior
of ngAnimate's $animate workflow. It is much better instead to just queue all
$animate animation calls into a queue collection which is available on the $animate
service when mock.animate is included as a module within test code.
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
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
chore(inputSpec): fixed typo 2014-01-07T00:37:47+00:00 Ben Wiklund 2014-01-06T04:01:33+00:00 eb90672aae0fae1fdcd8b05b14b04f1e6818662b 






fix(ngShow/ngHide, ngIf): functions with zero args should be truthy
2014-01-03T06:59:43+00:00

Brian Ford

2014-01-02T22:48:03+00:00

01c5be4681e34cdc5f5c461b7a618fefe8038919

Previously, expressions that were a function with one or more arguments evaluated to
true, but functions with zero arguments evaluated to false.

This behavior seems both unintentional and undesirable. This patch makes a function
truthy regardless of its number of arguments.

Closes #5414





Previously, expressions that were a function with one or more arguments evaluated to
true, but functions with zero arguments evaluated to false.

This behavior seems both unintentional and undesirable. This patch makes a function
truthy regardless of its number of arguments.

Closes #5414







fix(ngRepeat): allow for more flexible coding style in ngRepeat expression
2014-01-03T00:14:16+00:00

Gias Kay Lee

2014-01-02T16:22:10+00:00

c9705b755645a4bfe066243f2ba15a733c3787e1

With this change it's possible to split the ng-repeat expression into multiple
lines at any point in the expression where white-space is expected.

Closes #5537
Closes #5598





With this change it's possible to split the ng-repeat expression into multiple
lines at any point in the expression where white-space is expected.

Closes #5537
Closes #5598