For instance, scroll to the bottom of the list, open the details, and try to scroll up.
I did notice when creating this that the tab control has something to do with the problem. Without the tab control, scrolling is slow, but not freaky.
6 Answers, 1 is accepted
When you have row details, their height is not known prior to expanding them. The height can be any. That is why the whole scroll area height is constantly recalculated when row details are expanded. In other words, we cannot do the math beforehand, since we really don't know what will show up in the row details -- it can be 20px or 2000px. That is why we re-do the math each time we gain knowledge about the height of a row details. That is why it seems that the scroll-bar is jumping around. Unfortunately, there is nothing that we can do about this.
Kind regards,Ross
the Telerik team

Row Details are actually inside the row, so if you set an explicit row height, you may clip them. But you can go ahead and try this -- it may help in your particular scenario.
Greetings,Ross
the Telerik team

I am running out of ideas. Can you try these two:
A. Turn of vertical virtualization, so that all rows are realized.
B. Instead of Row Details, use Hierarchy. You will place the gauge and inner grid in a custom hierarchy tempalte. The UI elements inside the hierarchy template are not recycled, so this might help.
Greetings,
the Telerik team
