Results 1 to 3 of 3

Thread: Flickering controls in Touch 2.1.0/2.1.1 on iPhone/iPad?

  1. #1
    Sencha Premium Member
    Join Date
    May 2012
    Posts
    52
    Vote Rating
    12
      0  

    Default Flickering controls in Touch 2.1.0/2.1.1 on iPhone/iPad?

    We have a Touch 2.0 project written in Architect which work great viewed in the browser on all devices (no packaging). We upgraded to Touch 2.1.1 and it all works well except that now some of the controls momentarily flicker when transitioning state on iPhone and iPad, they do not flicker in Chrome on the desktop or Android devices like Kindle, or Samsung smartphones.

    For example, rectangular blocks of the title-bar of a nested list will momentarily become transparent when a list item is tapped. Or the bottom toolbar of a tabbed panel will momentarily disappear when navigating between panels by tapping the icons. We've tried CSS'ing the background on everything, placing the effected controls (nested lists in particular) inside CSSed containers has no effect - the blocks of transparency still goes all the way through to the page background color. Our theme is black so this really shows up - weve made the page background black which helps but the blocks of missing menu-bars etc. are still very apparently (since these are colored). Weve also turned auto-destroy off but that has no effect either. It just happens for of a second flash during the transition and only on iPhone/iPad. The Touch 2.0 version is rock solid and does not exhibit this behavior in any way.

    Theres probably something we dont know about that we should be doing in Touch 2.1.1 to prevent this so any help would be greatly appreciated.

    Thank you

  2. #2
    Sencha Premium Member
    Join Date
    Jul 2012
    Posts
    2
    Vote Rating
    0
      0  

    Default We have the exact same issue

    Any update on this?

  3. #3
    Sencha User aconran's Avatar
    Join Date
    Mar 2007
    Posts
    9,487
    Vote Rating
    145
      0  

    Default

    This sounds like it could possibly be a bug in Touch 2.1. Can either of you create a small test case which illustrates the behavior so that we can pass it along to the Touch team?
    Aaron Conran
    @aconran

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •