[data grid] Stop rendering when overscrolling on iOS

[BalaVJNorstella]

Steps to reproduce

Link to live example: (required)

Steps:

1. Go to https://mui.com/x/react-data-grid/#pro-plan in iPad
2. Scroll the Data grid which have rowHeight
3. You can see empty space in rendering, it looks like flickering

Current behavior

MicrosoftTeams-video.mp4

Flickering when scrolling vertically in iPad

Expected behavior

Mui Data Grid Pro render without flickering.

Context

We are facing flickering issue in iPad when scroll on Mui DataGrid.
We can see empty screen for few milliseconds, so it makes the page flickering.

https://mui.com/x/react-data-grid/#pro-plan - We can see same issue in this page in iPad.

We are using DataGridPro from mui/x-data-grid-pro.
iPadOS 17.7 (21H16)
iPad (10th generation)

We have tested some other tables in iPad, all are rendering fine.
Help us to resolve this issue.

Support key -> 77584 - Licenses (QT 23092601)

Your environment

No response

Search keywords: Flickering issue when rendering MUI Data Grid Pro in iPad
Order ID: 77584

[MBilalShafi]

It seems to be related to #14981 which has already been fixed.

Could you check if you can still reproduce the issue in https://deploy-preview-14983--material-ui-x.netlify.app/x/react-data-grid/

[BalaVJNorstella]

@MBilalShafi @oliviertassinari I'm still facing same issue in iPad.

MicrosoftTeams-video.1.mp4

I have checked it in mui website

[KenanYusuf]

Hi @BalaVJNorstella - I believe this is related to diagonal scrolling.

We have two issues open already with different options to fix this issue:

• [data grid] Prevent diagonal scrolling on iOS #11230
• [data grid] Support diagonal scrolling #13551

I will close this issue for now as I believe it will be fixed by one of the above.

[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

@BalaVJNorstella 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.

[oliviertassinari]

Reopening. It's a different problem than anything mentioned so far. It's a continuation of #269 and #443. We never truly fixed the problem, only a few cases when it happen each 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

@BalaVJNorstella 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.