You found a bug! We've classified it as TOUCH-5463 . We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
  1. #21
    Sencha User
    Join Date
    Jul 2011
    Location
    Pakistan
    Posts
    86
    Vote Rating
    2
    zonaib is on a distinguished road

      0  

    Default


    Thats great and thank you to provide us another solution.

  2. #22
    Sencha Premium Member
    Join Date
    Feb 2012
    Posts
    83
    Vote Rating
    2
    sencha-noob is on a distinguished road

      0  

    Default Still an issue on android 5; no suitable solution

    Still an issue on android 5; no suitable solution


    We continue to see this issue with some message boxes on some Android 5 devices. Among others, we've seen it on a Nexus running 5.0.1 in an iOS/Android cordova app. It doesn't happen with all message boxes, but the ones effected can easily replicate the problem with a few attempts at showing. It seems to only happen in the cases where we use the Ext.Msg singleton instead of creating a new Ext.MessageBox.

    It seems that the source of the issue is that in our case the transitionend event which is used in CssTransition.js to call onTransitionEnd is only fired once during the show animation in the cases where the message box breaks. onTransitionEnd is responsible for running refreshRunningAnimationsData. It looks like it should be run multiple times.

    On iOS and in other android version, the transitionend event is fired multiple times. The last time it's fired, refreshRunningAnimationsData calls onAnimationEnd & then onAllAnimationsEnd. Those animation end events are not called in the case the transitionend event is only fired 1x.

    According to the spec, transitionend should fire, unless the transition is removed before it completes. I'm not sure why it doesn't occur 100% of the time for all messageboxes, but absent the transitionend event firing again, the animation is never going to complete and call animationend, which can leave the message box and app in an unstable state.

    Although we've disabled the show animations - hide animation does not exhibit this problem - disabling animations is not a suitable solution & is merely a temporary hack.