angular.js/src/ng, 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
docs($interval): remind the developer to destroy their intervals 2013-12-19T13:46:30+00:00 Josh Kurz 2013-12-12T06:39:40+00:00 277a5ea05d50fb27243b98570c3ca9394b31e935 It is essential that users of `$interval` destroy the interval when they are finished. Otherwise you can get memory leaks. Often `$intervals` are used in directives or controllers and developers don't think about what happens when the component is destroyed. If a directive/controller scope is destroyed, then the $interval should be destroyed as well. This could cause some issues with developers who assume that the interval will be cleared for them when the scope is destroyed. Closes #5377 I believe that the library could/should handle this as well, but thats another issue. 
It is essential that users of `$interval` destroy the interval when they are finished.
Otherwise you can get memory leaks.
Often `$intervals` are used in directives or controllers and developers don't think
about what happens when the component is destroyed.
If a directive/controller scope is destroyed, then the $interval should be destroyed as well.
This could cause some issues with developers who assume that the interval will be cleared
for them when the scope is destroyed.

Closes #5377

I believe that the library could/should handle this as well, but thats another issue.
docs(ngCloak): style name is ng-cloak, not ngCloak 2013-12-19T13:32:19+00:00 snicolai 2013-12-12T03:49:52+00:00 9865a7c0ad678fa6a3daa2719e37d94aeb62f67b Closes #5374 
Closes #5374
docs(booleanAttrs): add @priority to all the boolean directives 2013-12-19T13:29:19+00:00 Mark Jones 2013-12-10T21:35:12+00:00 efba4731e4b22481f1c0b1c417ea24c00182095a Closes #5361 
Closes #5361
docs(ngEventDirs): adding quick examples for new events 2013-12-19T12:57:33+00:00 James Watling 2013-12-09T20:53:35+00:00 3d156a76e3501ea29fe7d208dc89f0ae89e76fc3 Closes #5338 
Closes #5338
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($log): should work in IE8 2013-12-19T05:44:00+00:00 Tobias Bosch 2013-12-19T02:52:36+00:00 4f5758e6669222369889c9e789601d25ff885530 In IE8, reading `console.log.apply` throws an error. Catching this errow now. Fixes #5400. Fixes #5147. 
In IE8, reading `console.log.apply` throws an error.
Catching this errow now.

Fixes #5400. Fixes #5147.
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