| commit | b3c009e1c35d1886c1d20ee414ce09911a9981d3 | |
| author | Sergio Crisostomo <sergiosbox@gmail.com> | |
| Fri, 23 May 2014 21:10:50 +0000 (23 23:10 +0200) | ||
| committer | Sergio Crisostomo <sergiosbox@gmail.com> | |
| Fri, 23 May 2014 21:10:50 +0000 (23 23:10 +0200) | ||
| tree | c3d46c17ce828004b350f356060d5ca29047e013 | treesnapshot (tar.gz zip) |
| parent | 0e2a1a69b3b400a26e04e1e35df04f827a90d476 | commitdiff |
Correct visibility when fading from onComplete
When a new fade is called inside the onComplete event of first fade out,
then the opacity fades as expected but the visibility will not be set
back to visible. This happens because the first fade sets the visibility
after the fade is done. So the onComplete actually fires before the
visibility is set.
When a new fade is called inside the onComplete event of first fade out,
then the opacity fades as expected but the visibility will not be set
back to visible. This happens because the first fade sets the visibility
after the fade is done. So the onComplete actually fires before the
visibility is set.
| Source/Fx/Fx.Tween.js | diffblobblamehistory | |
| Specs/Fx/Fx.Tween.js | diffblobblamehistory |