angular.js/src, branch v1.2.6

feat(ngAnimate): provide configuration support to match specific className values to trigger animations

2013-12-19T21:37:29+00:00

Closes #5357
Closes #5283

feat(jqLite): provide support for element.one()

2013-12-19T19:39:04+00:00

fix($animate): use a scheduled timeout in favor of a fallback property to close transitions

2013-12-19T17:01:12+00:00

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

docs($interval): remind the developer to destroy their intervals

2013-12-19T13:46:30+00:00

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

Closes #5374

docs(booleanAttrs): add @priority to all the boolean directives

2013-12-19T13:29:19+00:00

Closes #5361

docs($injector): use correct spacing convention for CoffeeScript functions

2013-12-19T13:05:15+00:00

This convention is exhibited by http://coffeescript.org/ and https://github.com/polarmobile/coffeescript-style-guide#functions.

Closes #5354

docs(ngEventDirs): adding quick examples for new events

2013-12-19T12:57:33+00:00

Closes #5338

fix($compile): remove invalid IE exceptional case for `href`

2013-12-19T12:22:58+00:00

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 `` elements.

Closes #5479

fix($parse): return 'undefined' if a middle key's value is null

2013-12-19T08:59:22+00:00

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