This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27.5k
ngAnimate breaks jquery.transit (and possibly other transform-based animations) under Chrome #6675
Milestone
Comments
+1 |
@matsko is this a known issue? |
I think it has to do with the ordering of the animations. I'm currently looking into it. |
SekibOmazic
added a commit
to SekibOmazic/angular.js
that referenced
this issue
Mar 19, 2014
…e fields extend compare method to use Date.valueOf() when comparing dates closes angular#6675
Please ignore the reference to the pull request 6746. It was just a typo in the commit message. PR 6746 refers to the issue 6676. |
+1 |
SekibOmazic
added a commit
to SekibOmazic/angular.js
that referenced
this issue
Mar 20, 2014
…e fields extend compare method to use Date.valueOf() when comparing dates closes angular#6675 remove custom isDate function - angular already has one
matsko
added a commit
to matsko/angular.js
that referenced
this issue
Mar 21, 2014
… inheritance If a JS animation is run before a CSS animation then the JS animation may end up writing style data to the element. If any transition or animation style data is written then it may end up being accidentally inherited into the CSS animation hanlder that ngAnimate uses. This may result in an unexpected outcome due to the tweaks and hacks that the CSS handler places on the element. If the CSS animation is run before the JS animation then, if there are no transitions on the style attribute nor within the global CSS on the page then nothing will happen and the JS animation can work as expected. Closes angular#6675
matsko
added a commit
to matsko/angular.js
that referenced
this issue
Mar 21, 2014
… inheritance If a JS animation is run before a CSS animation then the JS animation may end up writing style data to the element. If any transition or animation style data is written then it may end up being accidentally inherited into the CSS animation hanlder that ngAnimate uses. This may result in an unexpected outcome due to the tweaks and hacks that the CSS handler places on the element. If the CSS animation is run before the JS animation then, if there are no transitions on the style attribute nor within the global CSS on the page then nothing will happen and the JS animation can work as expected. Closes angular#6675
@bpampuch the code is fixed good sir: http://plnkr.co/edit/Gy4RZeDnIYvWGWessQfV?p=preview |
Waiting on #6799 to go in. |
matsko
added a commit
to matsko/angular.js
that referenced
this issue
Mar 26, 2014
… inheritance If a JS animation is run before a CSS animation then the JS animation may end up writing style data to the element. If any transition or animation style data is written then it may end up being accidentally inherited into the CSS animation hanlder that ngAnimate uses. This may result in an unexpected outcome due to the tweaks and hacks that the CSS handler places on the element. If the CSS animation is run before the JS animation then, if there are no transitions on the style attribute nor within the global CSS on the page then nothing will happen and the JS animation can work as expected. Closes angular#6675
Landed as 2317af6 |
matsko
added a commit
that referenced
this issue
Mar 26, 2014
… inheritance If a JS animation is run before a CSS animation then the JS animation may end up writing style data to the element. If any transition or animation style data is written then it may end up being accidentally inherited into the CSS animation hanlder that ngAnimate uses. This may result in an unexpected outcome due to the tweaks and hacks that the CSS handler places on the element. If the CSS animation is run before the JS animation then, if there are no transitions on the style attribute nor within the global CSS on the page then nothing will happen and the JS animation can work as expected. Closes #6675
And as 0e5106e for 1.2.x |
awesome ! :) thx |
+1 |
ckknight
pushed a commit
to ckknight/angular.js
that referenced
this issue
Jul 16, 2014
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm trying to animate transforms using JavaScript-based animations.
Although the above behaviour could be easily achieved using CSS, I need to use JS-animations (it's part of a bigger scenario).
Unfortunately this doesn't work under Chrome. The transform is immediately set to the final value.
The problem is, ngAnimate in its
animateSetup
disables the transition withblockTransitions
(as a workaround for a bug in Chrome/FF as it claims).Apparently this workaround leads to another bug under Chrome/FF.
http://plnkr.co/edit/z4sMCsDMvABPmvTnLzkp?p=preview
The text was updated successfully, but these errors were encountered: