[data grid] Scrolling with scrollbar jumps back to a previous position when getRowHeight={() => 'auto'} is used

[annawatson-wk]

Steps to reproduce

Link to live example: https://stackblitz.com/edit/react-sux3md?file=Demo.tsx

Steps:

1. Scroll down on the Data Grid using the scrollbar
2. Make note of which row id you're looking at when you're about to stop scrolling
3. Note that the row id after you've stopped scrolling, they are different

Current behavior

The row you're viewing when you release the scrollbar aren't the rows you see when you release the scrollbar. We don't see this behavior for a smaller number of rows where virtualization of rows doesn't come into play.

Expected behavior

The row you're viewing when you release the scrollbar are the rows you see when you release the scrollbar.

Context

We had a customer report this jumping behavior when they scroll using the scrollbar. The seems like this might be related to virtualization on the grid rows then those rows adjusting their size due to rowHeight auto. This was seen in version 6 and version 7 of mui-x. We're really looking for a way that we can make this virtualization/rowHeight behavior seem less clunky.

Your environment

npx @mui/envinfo

System:
    OS: macOS 13.6.2
  Binaries:
    Node: 20.8.1 - ~/.asdf/installs/nodejs/20.8.1/bin/node
    npm: 10.1.0 - ~/.asdf/plugins/nodejs/shims/npm
  Browsers:
    Chrome: 129.0.6668.71

Search keywords: scrollbar data grid jumping pro premium rowHeight
Order ID: 82849

[michelengelen]

Hey @annawatson-wk ... I can confirm this bug and it indeed seems like the virtualization is at fault here. The scrolling position is correct, however the scrollbar will jump back to a previous position once you stop scrolling. This can be easily reproduced by quickly scrolling and keeping the scrollbar clicked when stopping the scroll movement.

Screen.Recording.2024-10-02.at.16.35.33.mov

cc @romgrk

[annawatson-wk]

I just went back to change autoHeight to getRowHeight and didn't catch that you already did that. Thank you!

[romgrk]

Investigate #14808 at the same time.

[github-actions]

This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

Note

@annawatson-wk How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey.