angular.js/test, branch v1.2.6 feat(ngAnimate): provide configuration support to match specific className values to trigger animations 2013-12-19T21:37:29+00:00 Matias Niemelä 2013-12-16T20:45:57+00:00 cef084ade9072090259d8c679751cac3ffeaed51 Closes #5357 Closes #5283 
Closes #5357
Closes #5283
feat(jqLite): provide support for element.one() 2013-12-19T19:39:04+00:00 Matias Niemelä 2013-11-28T06:10:28+00:00 937caab6475e53a7ea0206e992f8a52449232e78 






style(animateSpec): ensure spacing between specs and describes is consistent
2013-12-19T17:02:00+00:00

Matias Niemelä

2013-12-19T16:56:26+00:00

3fc8017119497207c8e300e4014b4b2f62585bec












fix($animate): use a scheduled timeout in favor of a fallback property to close transitions
2013-12-19T17:01:12+00:00

Matias Niemelä

2013-12-14T05:30:48+00:00

54637a335f885110efaa702a3bab29c77644b36c

With ngAnimate, CSS transitions, that are not properlty triggered, are forceably closed off
by appling a fallback property. The fallback property approach works, however, its styling
itself may effect CSS inheritance or cause the element to render improperly. Therefore, its
best to stick to using a scheduled timeout to run sometime after the highest animation time
has passed.

Closes #5255
Closes #5241
Closes #5405





With ngAnimate, CSS transitions, that are not properlty triggered, are forceably closed off
by appling a fallback property. The fallback property approach works, however, its styling
itself may effect CSS inheritance or cause the element to render improperly. Therefore, its
best to stick to using a scheduled timeout to run sometime after the highest animation time
has passed.

Closes #5255
Closes #5241
Closes #5405







fix($compile): remove invalid IE exceptional case for `href`
2013-12-19T12:22:58+00:00

Alexandre Potvin Latreille

2013-12-19T12:21:14+00:00

c7a1d1ab0b663edffc1ac7b54deea847e372468d

It appears that this exceptional case was only valid for IE<8 and that for IE>=8 it
was actually causing a bug with the `ng-href-attr` directive on `<a>` elements.

Closes #5479





It appears that this exceptional case was only valid for IE<8 and that for IE>=8 it
was actually causing a bug with the `ng-href-attr` directive on `<a>` elements.

Closes #5479







fix($parse): return 'undefined' if a middle key's value is null
2013-12-19T08:59:22+00:00

Caitlin Potter

2013-12-19T04:52:31+00:00

26d43cacdc106765bd928d41600352198f887aef

Prior to this fix, $parse/$eval would return 'null' if a middle key in
an expression's value is null, when it should be expected to be undefined.

This patch tries to remedy this by returning undefined for middle values in
expressions, when fetching a child of that null value.

For example:

```js
// Given the following object:
$scope.a = {
  b: null
};

// $scope.$eval('a.b.c') returns undefined, whereas previously it would return null
```

Closes #5480





Prior to this fix, $parse/$eval would return 'null' if a middle key in
an expression's value is null, when it should be expected to be undefined.

This patch tries to remedy this by returning undefined for middle values in
expressions, when fetching a child of that null value.

For example:

```js
// Given the following object:
$scope.a = {
  b: null
};

// $scope.$eval('a.b.c') returns undefined, whereas previously it would return null
```

Closes #5480







fix(forEach): allow looping over result of querySelectorAll in IE8
2013-12-19T05:44:00+00:00

Tobias Bosch

2013-12-19T02:51:56+00:00

274a6734ef1fff543cc50388a0958d1988baeb57

In IE8 the result object
of calling `node.querySelectorAll` does not have a `hasOwnPropery`
function. However, it should be usable with `forEach`.

Related to #5400.





In IE8 the result object
of calling `node.querySelectorAll` does not have a `hasOwnPropery`
function. However, it should be usable with `forEach`.

Related to #5400.







fix($location): parse xlink:href for SVGAElements
2013-12-19T01:16:39+00:00

Caitlin Potter

2013-12-18T22:12:02+00:00

bc3ff2cecd0861766a9e8606f3cc2c582d9875df

Before this fix, the xlink:href property of an SVG <a> element could not be parsed
on click, as the property is an SVGAnimatedString rather than a DOMString.

This patch parses the xlink:href's animVal into a DOMString in order to prevent
an `Object #<SVGAnimatedString> has no method 'indexOf'` exception from being thrown,
and also to update the location if necessary as expected.

Closes #5472
Closes #5198
Closes #5199
Closes #4098
Closes #1420





Before this fix, the xlink:href property of an SVG <a> element could not be parsed
on click, as the property is an SVGAnimatedString rather than a DOMString.

This patch parses the xlink:href's animVal into a DOMString in order to prevent
an `Object #<SVGAnimatedString> has no method 'indexOf'` exception from being thrown,
and also to update the location if necessary as expected.

Closes #5472
Closes #5198
Closes #5199
Closes #4098
Closes #1420







perf($parse) use a faster path when the number of path parts is low
2013-12-18T23:44:15+00:00

Karl Seamon

2013-12-05T23:08:52+00:00

864b2596b246470cca9d4e223eaed720f4462319

Use a faster path when the number of path tokens is low (ie the common case).
This results in a better than 19x improvement in the time spent in $parse and
produces output that is about the same speed in chrome and substantially faster
in firefox.
http://jsperf.com/angularjs-parse-getter/6

Closes #5359





Use a faster path when the number of path tokens is low (ie the common case).
This results in a better than 19x improvement in the time spent in $parse and
produces output that is about the same speed in chrome and substantially faster
in firefox.
http://jsperf.com/angularjs-parse-getter/6

Closes #5359







fix(input): do not hold input for composition on android
2013-12-18T20:28:07+00:00

Chia-liang Kao

2013-12-18T08:28:35+00:00

3dc18037e8db8766641a4d39f0fee96077db1fcb

Workaround for chrome for android until #2129 is ready.

Closes #5308, #5323





Workaround for chrome for android until #2129 is ready.

Closes #5308, #5323