Success! Looks like we've fixed this one. According to our records the fix was applied for TOUCH-5463 in 2.4.3.
  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
    84
    Vote Rating
    2
    sencha-noob is on a distinguished road

      0  

    Default 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.

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

      0  

    Default This might help

    This latest detail might help someone fix the underlying problem. We found that if we override the popin & fade animations so that they don't change opacity, the problem went away. We're not sure if it's the opacity animation that's at fault or just reducing the number of transitions for the animation is what fixed it.

    Although this works fine on affected Android 5 webviews, it's caused problems on older webkit browsers. On older Android browsers not the animated object is super blury until the animation completes. It might be related to an old ant-aliasing issue and we haven't solved that issue yet.

    Are any sencha developers working to solve this serious issue?

  4. #24
    Sencha User
    Join Date
    Jul 2012
    Location
    bangalore
    Posts
    20
    Vote Rating
    0
    loki4u is on a distinguished road

      0  

    Default

    Hi,

    Ext.Msg.defaultAllowedConfig.showAnimation = false;

    in app.js inside the launch method might solve your issue :-)

  5. #25
    Sencha Premium Member
    Join Date
    Apr 2014
    Posts
    72
    Vote Rating
    1
    rsravishankar is on a distinguished road

      0  

    Default

    What is Sencha's recommended workaround for this for version 2.3.0 and I can't go to a higher version bcos this another UI issue (https://www.sencha.com/forum/showthread.php?289321 & Premium forum: https://www.sencha.com/forum/showthr...ards&p=1105753) Hope someone from Sencha can respond ASAP as my release is blocked on this.

  6. #26
    Sencha User
    Join Date
    Aug 2011
    Posts
    26
    Vote Rating
    0
    leebyeungok is on a distinguished road

      0  

    Default

    It occurrs.. 2.4 also..