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

RadzenSideBar forced to Expand on load #1809

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

Originally created by @Anspitzen on GitHub (Jul 15, 2025).

Describe the bug
Independently of the set/Bound Expanded Property the RadzenSideBar will render on Expanded on first Render

To Reproduce
Steps to reproduce the behavior:

  1. Go to Official Demo
  2. Edit Source bool value sidebar1Expanded to false;
  3. Run
  4. See error

Expected behavior
The pre-set value is adhered to and not overwritten on load in the sidebar internally

Desktop (please complete the following information):

  • Browser chrome
  • Version Latest of today

Additional context
If you set the Visible for the content of the sidebar to the same variable you will see that it is still the loaded value (false) but the sidebar is overwriting the value internally on first appearance. Afterwards it is correctly behaving with the variable

Originally created by @Anspitzen on GitHub (Jul 15, 2025). **Describe the bug** Independently of the set/Bound Expanded Property the RadzenSideBar will render on Expanded on first Render **To Reproduce** Steps to reproduce the behavior: 1. Go to [Official Demo](https://blazor.radzen.com/layout?theme=standard#sidebar-header-footer) 2. Edit Source bool value sidebar1Expanded to false; 3. Run 4. See error **Expected behavior** The pre-set value is adhered to and not overwritten on load in the sidebar internally **Desktop (please complete the following information):** - Browser chrome - Version Latest of today **Additional context** If you set the Visible for the content of the sidebar to the same variable you will see that it is still the loaded value (false) but the sidebar is overwriting the value internally on first appearance. Afterwards it is correctly behaving with the variable
claunia commented 2026-01-29 17:58:51 +00:00
Author
Owner
Copy Link

@akorchev commented on GitHub (Jul 15, 2025):

Duplicate of #716

@akorchev commented on GitHub (Jul 15, 2025): Duplicate of #716
claunia commented 2026-01-29 17:58:51 +00:00
Author
Owner
Copy Link

@Anspitzen commented on GitHub (Jul 17, 2025):

Thanks, didn't see that one.
To prevent same question again, maybe put in documentation for the Expanded Sidebar, mentioning potential Side-effects from the Responsive Parameter (which is default true and not visible to check without knowing it exists and what it does)

@Anspitzen commented on GitHub (Jul 17, 2025): Thanks, didn't see that one. To prevent same question again, maybe put in documentation for the Expanded Sidebar, mentioning potential Side-effects from the Responsive Parameter (which is default true and not visible to check without knowing it exists and what it does)
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#1809
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?