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
I tried the new Loading state of the FluentDataGrid and experienced some unexpected behaviors.
If I fetch data and get 0 items back, the loading animation keeps on spinning instead of displaying the EmptyContent fragment.
Another one was that I don't get the loading animation if I have already fetched some items and trigger additonal remote data fetches afterwards.
After the remote data got fetched and the result contains 0 items, the data grid should leave the loading state and render the EmptyContent fragment.
馃槸 Current Behavior
Because the item count of the result isn't greater than 0 the data grid doesn't set loading to false and keeps displaying the LoadingContent fragment.
馃拋 Possible Solution
My naive guess would be that don't checking the _ariaBodyRowCount for Loading state features would fix this issue.
For example in FluentDataGrid.razor:33 and FluentDataGrid.razor.cs:371.
But then also the check in FluentDataGrid.razor.cs:375 must be removed because otherwise no rendering of the EmptyContent will occure.
But maybe I miss something because these got added intentionally to fix some LoadingContent issues in c3933e2
// Please let us know if you'd be willing to contribute the fix; we'd be happy to work with you
Yes
馃敠 Context
I used BlazorWasm.
My use case is a list page with pagination that fetches remote data for the current page to display.
A result with zero items is a valid result which should tell the user that there is no data here.
Also if I issue a filter/search or navigate between pages, it may be benefical to display the LoadingContent again, which doesn't happen because of already displayed items, even if the Grid state is set to Loading=true again.
馃實 Your Environment
OS & Device: [e.g. MacOS, iOS, Windows, Linux] on [iPhone 7, PC]
Browser Edge, Chrome, Firefox
.NET and FAST Version .NET8 and FAST 4.4
The text was updated successfully, but these errors were encountered:
馃悰 Bug Report
I tried the new Loading state of the FluentDataGrid and experienced some unexpected behaviors.
If I fetch data and get 0 items back, the loading animation keeps on spinning instead of displaying the EmptyContent fragment.
Another one was that I don't get the loading animation if I have already fetched some items and trigger additonal remote data fetches afterwards.
馃捇 Repro or Code Sample
馃 Expected Behavior
After the remote data got fetched and the result contains 0 items, the data grid should leave the loading state and render the EmptyContent fragment.
馃槸 Current Behavior
Because the item count of the result isn't greater than 0 the data grid doesn't set loading to false and keeps displaying the LoadingContent fragment.
馃拋 Possible Solution
My naive guess would be that don't checking the _ariaBodyRowCount for Loading state features would fix this issue.
For example in FluentDataGrid.razor:33 and FluentDataGrid.razor.cs:371.
But then also the check in FluentDataGrid.razor.cs:375 must be removed because otherwise no rendering of the EmptyContent will occure.
But maybe I miss something because these got added intentionally to fix some LoadingContent issues in c3933e2
// Please let us know if you'd be willing to contribute the fix; we'd be happy to work with you
Yes
馃敠 Context
I used BlazorWasm.
My use case is a list page with pagination that fetches remote data for the current page to display.
A result with zero items is a valid result which should tell the user that there is no data here.
Also if I issue a filter/search or navigate between pages, it may be benefical to display the LoadingContent again, which doesn't happen because of already displayed items, even if the Grid state is set to Loading=true again.
馃實 Your Environment
The text was updated successfully, but these errors were encountered: