.net9 Virtualize has a new property MaxItemCount, breaks MudVirtualize for larger OverscanCount values

Things to check

[X] I have searched the existing issues for this bug
[X] To rule out a caching problem I made sure the bug also happens in an incognito tab

Bug type

Component

Component name

MudVirtualize

What happened?

.net9 seems to have introduced a new property Virtualize.MaxItemCount which defaults to 100.

When using e.g. a MudDataGrid with virtualized server data, the GridStateVirtualize.Count is never more than 100 regardless of the calculated Count based on the OverscanCount.

The MudDataGrid/MudVirtualize uses its calculated Count to ask for more data so if you have a OverscanCount of 50 you might expect the Count to perhaps be 110 but the returned rows are only 100 so after scrolling to the 100th row and keep scrolling you get blank lines until the 110th row is scrolled to and then the data refreshes.

I had a play and hardcoded a big MaxItemCount in the MudVirtualize code and it then gives the expected behaviour, not sure if you want a MaxItemCount on MudVirtualize with a big default value? Not sure why the MaxItemCount on .net9 Virtualize has been added though.

Expected behavior

.net9 works like .net8 and respects larger OverscanCount values.

Reproduction link

https://try.mudblazor.com/snippet/mEGSbFcOUPMnRyBl

Reproduction steps

The try.mudblazor snippet above will just be .net8, if there isn't a .net9 try.mudblazor then it works fine with the tmb repo code or any other project and shows the problem.

Relevant log output

No response

Version (bug)

7.15

Version (working)

No response

What browsers are you seeing the problem on?

Firefox, Chrome

On which operating systems are you experiencing the issue?

Windows

Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

MudBlazor / MudBlazor