Hi,

Which native scrolling mode do you refer to - the mobile application level or the view level? As far as I tested, our demos work as expected (the mobile forms view uses native scrolling).

Regards,
Petyo
Telerik

We only use native scrolling on view level, because on application level we encountered a scroll position problem on first load, where the header overlays the listview. Therefore we only use it on view level.The problem occures when switch from one view with only one bound listview to a view with some description labels on top and a bound list on the bottom. After the transition scrolling stops working on the new chrome version. With the old chrome version or with deactivated native scrolling it´s working again. I will try to make a dojo on monday!

Unfortunatly I was not able to show our problem within a dojo. Because of that I tried to dig a little bit deeper within our project and found a workaround in disabling the slide view transition. With the default transition it works as it should. It´s also working when I switch the user agent to e.g. iOS even on an Android device running chrome. 

I found a way to demonstrate you the problem! It was not working within a dojo, because it only works with remote views! ;-)

I created a very simple sample application to show you the effect I described.

You have to use Chrome (in my case 38.0.2125.101 on my windows desktop machine) and activate the developer tools. Then emulate e.g. a NEXUS 4. (or use a android device with the current chrome app installed)

Open the overview.html, select a detail and go back to the overview. There is also a display problem with the detail arrow, but the main problem is the broken scrolling.

Hello,

I tried to reproduce the problem on my side, to no avail. Please check the recorded video. Chrome is the same version. 

Regards,
Petyo
Telerik

I tried to attach you a recorded demo of my pc, but the attachment size is to big. Have you tried it on a android phone?

At the moment we had to deactivate all view transitions, because every time we use a slide or fade, it stops working after the reverse transition.

I tested it on my private MAC with the current chrome version and it works! It´s not working on chrome for windows AND an android! ;-)

Hello,

thank you for the details - I managed to reproduce the issue on a windows machine. It definitely seems like a glitch which will be resolved soon. I will look for a bug, most likely already filed. 

Meanwhile, I managed to workaround the issue using the following approach - 



Regards,
Petyo
Telerik

Thank you for the workaround! Works perfectly! :-)

How do we know when the bug is fixed?

Hi,

we are going to revisit this issue when the next major version of Chrome comes up, and see if it is addressed. 

Regards,
Petyo
Telerik