GitHub Issue | n/a |
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2012-01-24T15:45:15.000+0000 |
Affected Version/s | Release 2.0.0 |
Fix Version/s | Sprint 2012-02, Release 2.0.0, Release 1.8.1 |
Components | MobileWeb |
Labels | qe-port, stage |
Reporter | Chris Barber |
Assignee | Chris Barber |
Created | 2012-01-10T14:18:59.000+0000 |
Updated | 2012-08-10T11:57:54.000+0000 |
When a UI element is animating and then is destroyed, make sure the callback is not fired. Need to experiment with removing the transition end event and with removing the transition settings from the element node.
This ticket is invalid because the act of removing the DOM node effectively cancels the animation.
OK, found a case where the browser is computing something big and decides destroy the element that had an animation complete while it was crunching.
Pull request: https://github.com/appcelerator/titanium_mobile/pull/1237
Verified fix on: Titanium studio : 2.1.1.201207271312 SDK version : 2.2.0.v20120810080115 Android 4.0.4 - default ,chrome 18.0 Iphone 4.3.5 - safari mobile Mountain lion(10.8) - chrome 21.0,safari 6,firefox 14.0.1