This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
1.2.0 ngClass transition animations broken in IE10+ #5014
Milestone
Comments
Closed
matsko
added a commit
to matsko/angular.js
that referenced
this issue
Nov 22, 2013
…dom operation occurs Transitions are blocked when the base CSS class is added at the start of the animation. This causes an issue if the followup CSS class contains animatable-styles. Now, once the animation active state is triggered (when the animation CSS dom operation occurs) the animation itself will always trigger an animate without a quick jump. Closes angular#5014 Closes angular#4265
jamesdaily
pushed a commit
to jamesdaily/angular.js
that referenced
this issue
Jan 27, 2014
…dom operation occurs Transitions are blocked when the base CSS class is added at the start of the animation. This causes an issue if the followup CSS class contains animatable-styles. Now, once the animation active state is triggered (when the animation CSS dom operation occurs) the animation itself will always trigger an animate without a quick jump. Closes angular#5014 Closes angular#4265
jamesdaily
pushed a commit
to jamesdaily/angular.js
that referenced
this issue
Jan 27, 2014
…dom operation occurs Transitions are blocked when the base CSS class is added at the start of the animation. This causes an issue if the followup CSS class contains animatable-styles. Now, once the animation active state is triggered (when the animation CSS dom operation occurs) the animation itself will always trigger an animate without a quick jump. Closes angular#5014 Closes angular#4265
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
$animate temporarily disables transitions for the setup class (ng-enter, ng-leave, class-add, etc...) such that the starting transitions styles are always applied properly. This has caused IE10/IE11 to break (an perhaps other browsers) in the event that the setup class is not present.
Test this page (using IE10 or IE11) to see:
http://plnkr.co/edit/zirJrJ70S9zDgGeMTYwq?p=preview
The text was updated successfully, but these errors were encountered: