You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using bUnit in the Microsoft Fluent UI Blazor library. We are seeing testing errors with .NET 11 RC1 while testing our DataGrid that uses Virtualize.
This is the analysis from the Copilot Debugger:
Root cause is confirmed.
The exception is not caused by your itemsProvider lambda or RefreshItems binding in FluentDataGrid_ItemsProvider.
It is thrown inside bUnit’s Virtualize JS interop handler during render initialization.
Evidence from the debugged sources:
bUnit invokes OnSpacerBeforeVisible with 3 arguments:
VirtualizeJSRuntimeInvocationHandler.cs:44-45
object[] parameters = new object[3] { 0f, 0f, 1E+09f };
In .NET 11, ASP.NET Core’s VirtualizeJsInterop.OnSpacerBeforeVisible expects 4 parameters:
VirtualizeJsInterop.cs:34
OnSpacerBeforeVisible(float spacerSize, float spacerSeparation, float containerSize, int reason)
This makes sense. The Virtualize component relies heavily on JSInterop, and bUnit does not run any JavaScript, so we provide a mock for the JSInterop interactions out of the box. However, the box has changed it seems, so we need to update it for the dotnet 11 release.
Since copilot already have its fingers down in the dirt, you should feel free to submit a PR to us that fixes this for dotnet 11.
As I am not familiar with this codebase and repo yet (just an end-user until now), is there a document that describes the process you (want me to) use for this? And which branch should I use?
Activity
egil commentedon Sep 9, 2026
Hi @vnbaaij
This makes sense. The Virtualize component relies heavily on JSInterop, and bUnit does not run any JavaScript, so we provide a mock for the JSInterop interactions out of the box. However, the box has changed it seems, so we need to update it for the dotnet 11 release.
Since copilot already have its fingers down in the dirt, you should feel free to submit a PR to us that fixes this for dotnet 11.
vnbaaij commentedon Sep 9, 2026
Sure, i can give it a shot.
As I am not familiar with this codebase and repo yet (just an end-user until now), is there a document that describes the process you (want me to) use for this? And which branch should I use?See #1919 for the result