angular.js, branch v1.2.6

chore(release): cut v1.2.6 release

2013-12-19T23:50:07+00:00

chore(release): improve the release script

2013-12-19T23:47:26+00:00

docs(CHANGELOG): add v1.2.6 changes

2013-12-19T21:55:10+00:00

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

style(animateSpec): ensure spacing between specs and describes is consistent

2013-12-19T17:02:00+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