Our use case is a "search filter" grid:

This "search filter" has the following characteristics:

1) It can potentially result in 1000's of rows being "found" by the search criteria, the actual search is done by the server using various HTTP(S) REST API's.

2) Obviously we only load a small initial number of rows from the server and then as the user scrolls down we load additional rows from the server as required.

3) The initial load of rows and the incremental subsequent load of rows are all done asynchronous using various HTTP(S) REST API's, so the new rows arrive asynchronous. While loading rows, the user is allowed to scroll freely in the already loaded rows. For the rows being loaded we show skeleton rows if the user scrolls into the area of the "search filter" currently being loaded.

We would request a update to the Kendo Grid libs. to support concurrent scrolling, loading of data (trough the pageChangeEven) and virtual rows & columns, all at the same time.