Galaxy Tab scroll issue after having changed a switch

3 posts, 0 answers
  1. Gareth
    Gareth avatar
    8 posts
    Member since:
    Jun 2012

    Posted 06 Apr 2012 Link to this post

    Hi,

    Strange one this. On my Galaxy Tab when I scroll the page, any switches that have been put into the OFF or NO state flick back to ON/YES while my finger is in the swipe motion. Also, the image of Eduardo disappears for the duration of the swipe too.

    Steps to reproduce :

    1) On a Galaxy Tab browse to http://www.captainsjob.com/test/kendouimobile/examples/mobile/switch/index.html 

    2) Change any of the switches to the OFF position

    3) Swipe the screen up and down

    This doesn't happen on the Dolphin browser, it happens on the default browser with Gingerbread 2.3.3. This browser lets you move a page up and down even if the entire page content is 100% visible.

    Fiddling about with the switches makes the previously change switch toggle back briefly too. Probably part of the same problem.

    Thanks
    Gareth
  2. Kamen Bundev
    Admin
    Kamen Bundev avatar
    1532 posts

    Posted 11 Apr 2012 Link to this post

    Hi Gareth,

    Thank you for reporting this issue. I've seen similar issues on some devices, usually related to the missing hardware acceleration in Android 2.3 which also varies with every manufacturer implementation. Unfortunately we don't have the first Galaxy Tab tablets here, but I know where to find one. I'll try to reproduce the issue on the real device and will get back to you with the result.

    All the best,
    Kamen Bundev
    the Telerik team
    Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
  3. Kendo UI is VS 2017 Ready
  4. Kamen Bundev
    Admin
    Kamen Bundev avatar
    1532 posts

    Posted 19 Apr 2012 Link to this post

    Hi Gareth,

    This is the same issue as the other one you reported - Galaxy Tab's default browser for some reason doesn't refresh its memory buffer before starting to scroll, which results in the old contents staying on screen while you drag. If you open the browser menu before scrolling, the contents get refreshed and this doesn't happen. We will try to come up with a fix for this issue, but meanwhile you ca try to disable the native scrolling in your app - check your other post for an example. I also updated your points for the find.

    All the best,
    Kamen Bundev
    the Telerik team
    Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
Back to Top