starred/radzen-blazor
1
0
Fork 0
mirror of https://github.com/radzenhq/radzen-blazor.git synced 2026-02-04 05:35:44 +00:00
Code Issues 1.3k Packages Projects Releases 22 Wiki Activity

RadzenDataGrid Group Row Collapse/Expanse Issue When Initially Collapsed #376

New Issue
Closed
opened 2026-01-29 17:36:15 +00:00 by claunia · 2 comments
claunia commented 2026-01-29 17:36:15 +00:00
Owner
Copy Link

Originally created by @Jerry239 on GitHub (Apr 18, 2022).

Describe the bug
Prerequisite: GroupFootersAlwaysVisible="true" for RadzenDataGrid
When all groups in a DataGrid are initially collapsed (through GroupRowRender Event, args.Expanded = false), all groups will be expanded when the user expands one group and collapses it again. Afterwards, the expand/collapse feature works as expected.

To Reproduce
The issue can easily be reproduced with the RadzenBlazorDemos project
Steps to reproduce the behavior:

  1. Edit DataGridGroupingApiPage.razor:
  • Add GroupFootersAlwaysVisible="true" to RadzenDataGrid
  • It is not necessary to add group footer templates for the bug to show
  • Edit OnGroupRowRender event handler to collapse all groups on first render:
    Line 67ff: if (args.FirstRender)
    {
    args.Expanded = false;
    }
  • Start demo and navigate to /datagrid-grouping-api
  • All groups should be collapsed now
  • Expand any group
  • Now collapse that group again
    -> All groups are expanding now. Only the group selected for collapsing is closed.

Expected behavior
Only the selected group should collapse. No other groups should expand

Desktop (please complete the following information):

  • OS: Microsoft Windows [Version 10.0.19044.1645]
  • Browser: Chrome 100.0.4896.88
  • Radzen 3.18.3
Originally created by @Jerry239 on GitHub (Apr 18, 2022). **Describe the bug** Prerequisite: GroupFootersAlwaysVisible="true" for RadzenDataGrid When all groups in a DataGrid are initially collapsed (through GroupRowRender Event, args.Expanded = false), all groups will be expanded when the user expands one group and collapses it again. Afterwards, the expand/collapse feature works as expected. **To Reproduce** The issue can easily be reproduced with the RadzenBlazorDemos project Steps to reproduce the behavior: 1. Edit DataGridGroupingApiPage.razor: - Add GroupFootersAlwaysVisible="true" to RadzenDataGrid - It is not necessary to add group footer templates for the bug to show - Edit OnGroupRowRender event handler to collapse all groups on first render: Line 67ff: if (args.FirstRender) { args.Expanded = false; } - Start demo and navigate to /datagrid-grouping-api - All groups should be collapsed now - Expand any group - Now collapse that group again -> All groups are expanding now. Only the group selected for collapsing is closed. **Expected behavior** Only the selected group should collapse. No other groups should expand **Desktop (please complete the following information):** - OS: Microsoft Windows [Version 10.0.19044.1645] - Browser: Chrome 100.0.4896.88 - Radzen 3.18.3
claunia commented 2026-01-29 17:36:17 +00:00
Author
Owner
Copy Link

@djuchems commented on GitHub (Apr 19, 2022):

Thanks for creating this issue, we have exactly the same problem. Initial collapsing via OnGroupRowRender and GroupFootersAlwaysVisible=true leads to this malfunction when collapsing and expanding groups afterwards.

@djuchems commented on GitHub (Apr 19, 2022): Thanks for creating this issue, we have exactly the same problem. Initial collapsing via _OnGroupRowRender_ and _GroupFootersAlwaysVisible=true_ leads to this malfunction when collapsing and expanding groups afterwards.
claunia commented 2026-01-29 17:36:17 +00:00
Author
Owner
Copy Link

@daletman commented on GitHub (Apr 25, 2022):

The Bug is fixed but in this exact scenario the first click after a freshly loaded page on the expand arrow of a collapsed group is ignored. The second click works just fine.

@daletman commented on GitHub (Apr 25, 2022): The Bug is fixed but in this exact scenario the first click after a freshly loaded page on the expand arrow of a collapsed group is ignored. The second click works just fine.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
good first issue
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/radzen-blazor#376
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?