Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DataGrid Incremental Loading not working when the height of the rows is less than the total available CellsHeight #4891

Open
11 of 14 tasks
filipwa84 opened this issue Jun 2, 2023 · 1 comment · May be fixed by #4892
Open
11 of 14 tasks
Labels
bug 🐛 An unexpected issue that highlights incorrect behavior In-PR 🚀

Comments

@filipwa84
Copy link
Contributor

filipwa84 commented Jun 2, 2023

Describe the bug

When using a collection that supports incremental loading, and the implementation of ISupportIncrementalLoading allows you to specify how many rows are retrieved on each load, then the DataGrid won't continue to load more data after the first set of data is retrieved if the height of the rows it receives is smaller than the available space for cells in the DataGrid.

The only way to get the DataGrid to load more data is to resize the window so that the available cell space is smaller than the total cell height.

Regression

No response

Reproducible in sample app?

  • This bug can be reproduced in the sample app.

Steps to reproduce

1. Setup a DataGrid with incremental loading from some collection
2. Use an implementation of ISupportIncrementalLoading that allows you to specify the number of rows to be retrieved in the paging operation.
3. Set the page size to a low number
4. Run the application
5. Only the first page will be loaded

Expected behavior

The DataGrid should continue to load data until the CellsHeight is full or there is no more data to load.

Screenshots

No response

Windows Build Number

  • Windows 10 1809 (Build 17763)
  • Windows 10 1903 (Build 18362)
  • Windows 10 1909 (Build 18363)
  • Windows 10 2004 (Build 19041)
  • Windows 10 20H2 (Build 19042)
  • Windows 10 21H1 (Build 19043)
  • Windows 11 21H2 (Build 22000)
  • Other (specify)

Other Windows Build number

No response

App minimum and target SDK version

  • Windows 10, version 1809 (Build 17763)
  • Windows 10, version 1903 (Build 18362)
  • Windows 10, version 1909 (Build 18363)
  • Windows 10, version 2004 (Build 19041)
  • Other (specify)

Other SDK version

No response

Visual Studio Version

No response

Visual Studio Build Number

No response

Device form factor

No response

Nuget packages

No response

Additional context

No response

Help us help you

Yes, I'd like to be assigned to work on this item.

@filipwa84 filipwa84 added the bug 🐛 An unexpected issue that highlights incorrect behavior label Jun 2, 2023
@ghost ghost added the needs triage 🔍 label Jun 2, 2023
@ghost
Copy link

ghost commented Jun 2, 2023

Hello filipwa84, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

@filipwa84 filipwa84 linked a pull request Jun 2, 2023 that will close this issue
4 tasks
@ghost ghost added In-PR 🚀 and removed needs triage 🔍 labels Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 An unexpected issue that highlights incorrect behavior In-PR 🚀
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant