angular.js/test/ng, 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($compile) support templates with table content root nodes 2014-02-14T19:42:55+00:00 Caitlin Potter 2013-12-02T20:05:21+00:00 31c450bcee53d0a3827b7e0a611e9013b2496506 If the first element in a template is a <tr>, <th>, <td>, or <tbody> tag, the HTML compiler will ensure that the template is wrapped in a <table> element so that the table content is not discarded. Closes #2848 Closes #1459 Closes #3647 Closes #3241 
If the first element in a template is a <tr>, <th>, <td>, or <tbody> tag,
the HTML compiler will ensure that the template is wrapped in a <table>
element so that the table content is not discarded.

Closes #2848
Closes #1459
Closes #3647
Closes #3241
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
feat(filterFilter): support deeply nested predicate objects 2014-02-11T22:08:41+00:00 Caitlin Potter 2014-02-11T14:57:04+00:00 b4eed8ad94ce9719540462c1ee969dfd3c6b2355 Due to 339a165, it became impossible to filter nested properties of an object using the filterFilter. A proposed solution to this was to enable the use of nested predicate objects. This change enables the use of these nested predicate objects. Example: ```html <div ng-repeat="it in items | filter:{ address: { country: 'Canuckistan'}}"></div> ``` Or ```js $filter('filter')(items, { address: { country: 'Canuckistan' } }); ``` Closes #6215 Related to #6009 
Due to 339a165, it became impossible to filter nested properties of an object using the filterFilter.
A proposed solution to this was to enable the use of nested predicate objects. This change enables the
use of these nested predicate objects.

Example:

```html
<div ng-repeat="it in items | filter:{ address: { country: 'Canuckistan'}}"></div>
```

Or

```js
$filter('filter')(items, { address: { country: 'Canuckistan' } });
```

Closes #6215
Related to #6009
fix($compile): ensure element transclusion directives are linked with comment element 2014-02-10T23:41:28+00:00 Caitlin Potter 2014-01-28T16:34:01+00:00 e7338d3f27e8824196136a18e1c3e0fcf51a0e28 This corrects a complicated compiler issue, described in detail below: Previously, if an element transclusion directive contained an asynchronous directive whose template contained another element transclusion directive, the inner element transclusion directive would be linked with the element, rather than the expected comment node. An example manifestation of this bug would look like so: ```html <div ng-repeat="i in [1,2,3,4,5]"> <div my-directive> </div> </div> ``` `my-directive` would be a replace directive, and its template would contain another element transclusion directive, like so: ```html <div ng-if="true">{{i}}</div> ``` ngIf would be linked with this template content, rather than the comment node, and the template element would be attached to the DOM, rather than the comment. As a result, this caused ng-if to duplicate the template when its expression evaluated to true. Closes #6006 Closes #6101 
This corrects a complicated compiler issue, described in detail below:

Previously, if an element transclusion directive contained an asynchronous directive whose template
contained another element transclusion directive, the inner element transclusion directive would be
linked with the element, rather than the expected comment node.

An example manifestation of this bug would look like so:

```html
<div ng-repeat="i in [1,2,3,4,5]">
  <div my-directive>
  </div>
</div>
```

`my-directive` would be a replace directive, and its template would contain another element
transclusion directive, like so:

```html
<div ng-if="true">{{i}}</div>
```

ngIf would be linked with this template content, rather than the comment node, and the template element
would be attached to the DOM, rather than the comment. As a result, this caused ng-if to duplicate the
template when its expression evaluated to true.

Closes #6006
Closes #6101
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($q): make $q.reject support `finally` and `catch` 2014-01-31T19:38:06+00:00 Lucas Galfasó 2014-01-31T18:22:36+00:00 074b0675a1f97dce07f520f1ae6198ed3c604000 Add support for the functions `finally` and `catch` to the promise returned by `$q.reject` Closes #6048 Closes #6076 
Add support for the functions `finally` and `catch` to the
promise returned by `$q.reject`

Closes #6048
Closes #6076
fix($compile): retain CSS classes added in cloneAttachFn on asynchronous directives 2014-01-31T17:45:35+00:00 Caitlin Potter 2014-01-03T16:50:53+00:00 5ed721b9b5e95ae08450e1ae9d5202e7f3f79295 Previously, classes added to asynchronous directive elements during the clone attach function would not persist after the node is merged with the template, prior to linking. This change corrects this behaviour and brings it in line with synchronous directives. Closes #5439 Closes #5617 
Previously, classes added to asynchronous directive elements during the clone
attach function would not persist after the node is merged with the template, prior
to linking. This change corrects this behaviour and brings it in line with synchronous
directives.

Closes #5439
Closes #5617
fix(filterFilter): don't interpret dots in predicate object fields as paths 2014-01-31T11:16:46+00:00 Igor Minar 2014-01-28T01:35:27+00:00 339a1658cd9bfa5e322a01c45aa0a1df67e3a842 Closes #6005 Closes #6009 
Closes #6005
Closes #6009