Hello,
The described behavior is due to a major changes of the scroll functionality in Chrome 32.
This issue is already fixed and will be available in the upcoming official release of RadControls suite, which will be released at the end of this month.
For the time being you can use the following example setup for workaround:
Regards,
Ianko
Telerik
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to the
blog feed now.