angular-message-format
Advanced tools
Changelog
1.4.0-rc.2 rocket-zambonimation (2015-05-12)
ng-anchor
instead of a suffixed -anchor
CSS class when triggering anchor animations
(df24410c)ng-animate-anchor
to ng-anchor
(e6d053de)ng-animate
class with classNameFilter
(1002b80a,
#11431, #11807)// before
var animator = $animateCss(element, { ... });
if (!animator) {
continueApp();
return;
}
var runner = animator.start();
runner.done(continueApp);
runner.then(continueApp);
// now
var animator = $animateCss(element, { ... });
var runner = animator.start();
runner.done(continueApp);
runner.then(continueApp);
Instead just use the ng-anchor
CSS class like so:
<div class="container-animation" ng-if="on">
<div ng-animate-ref="1" class="my-anchor-element"></div>
</div>
<div class="container-animation" ng-if="!on">
<div ng-animate-ref="1" class="my-anchor-element"></div>
</div>
before:
/* before (notice the container-animation CSS class) */
.container-animation-anchor {
transition:0.5s linear all;
}
now:
/* now (just use `ng-anchor` on a class that both the
elements that contain `ng-animate-ref` share) */
.my-anchor-element.ng-anchor {
transition:0.5s linear all;
}
due to e6d053de,
if your CSS code made use of the ng-animate-anchor
CSS class for referencing the anchored animation element then your
code must now use ng-anchor
instead.
due to 1002b80a,
partially or fully using a regex value containing
ng-animate
as a token is not allowed anymore. Doing so will trigger a
minErr exception to be thrown.
So don't do this:
// only animate elements that contain the `ng-animate` CSS class
$animateProvider.classNameFilter(/ng-animate/);
// or partially contain it
$animateProvider.classNameFilter(/some-class ng-animate another-class/);
but this is OK:
$animateProvider.classNameFilter(/ng-animate-special/);
Although it is unlikely that anyone is using it in this way, this change does change the
behavior of ngOptions
in the following case:
ngOptions
syntax
(item.label for item in items
) and that object contains non-numeric property keys.In this case these properties with non-numeric keys will be ignored.
** Here array-like is defined by the result of a call to this internal function: https://github.com/angular/angular.js/blob/v1.4.0-rc.1/src/Angular.js#L198-L211 **
To get the desired behavior you need to iterate using the object form of the ngOptions
syntax
(value.label
for (key, value) in items)`).
<a name="v1.4.0-rc.1"></a>
Changelog
v1.4.0-rc.1 sartorial-chronography (2015-04-24)
ng-anchor-in
is used
(3333a5c3)<a name="v1.4.0-rc.0"></a>