Hi Simon,
It appears that the specific databinding technique used in the mockup example manages to circumvent the algorithms, which take care of preventing the issue with the incorrect rows being shown. Please usе an approach similar to one of the following:
http://demos.telerik.com/kendo-ui/grid/virtualization-remote-data
http://demos.telerik.com/kendo-ui/grid/virtualization-local-data
One more thing that you can do is force the Grid dataSource to make requests only after the user stops scrolling. This is achieved by executing the following line before initializing the Grid:
Regards,
Dimo
Telerik
It appears that the specific databinding technique used in the mockup example manages to circumvent the algorithms, which take care of preventing the issue with the incorrect rows being shown. Please usе an approach similar to one of the following:
http://demos.telerik.com/kendo-ui/grid/virtualization-remote-data
http://demos.telerik.com/kendo-ui/grid/virtualization-local-data
One more thing that you can do is force the Grid dataSource to make requests only after the user stops scrolling. This is achieved by executing the following line before initializing the Grid:
kendo.ui.VirtualScrollable.fn.options.prefetch = false;Regards,
Dimo
Telerik
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!