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

[RadzenDropDown] ClearSearchAfterSelection does not reset filtering after reopening dropdown #1943

New Issue
Closed
opened 2026-01-29 18:15:56 +00:00 by claunia · 0 comments
claunia commented 2026-01-29 18:15:56 +00:00
Owner
Copy Link

Originally created by @daniel-almeida-vfxplc on GitHub (Dec 22, 2025).

Description
When using RadzenDropDown with the parameter ClearSearchAfterSelection="true", the search input is cleared after selecting an item (as expected), but the filtering applied previously remains active when reopening the dropdown.

Versions

Radzen.Blazor: 8.4.1 (previously 7.1.6 without this issue)
.NET: 10
Render mode: Blazor Server

Steps to reproduce

  1. Open the playground: https://blazor.radzen.com/playground/b4a001f4-f612-43e2-87d5-06779f197769
  2. Expand the dropdown and type something in the search input.
  3. Select one of the filtered options — the dropdown collapses (expected).
  4. Reopen the dropdown:
  • The search input is empty (expected because ClearSearchAfterSelection is true).
  • However, the filtering is still applied based on the previous search value (unexpected).
  1. Typing a new value or pressing backspace resets the filtering correctly.

Expected behavior
When reopening the dropdown, the search input should be empty and no filtering should be applied.

Actual behavior
The search input is cleared visually, but the filtering logic still uses the previous search value until the user types again.

Minimal reproduction
Playground link: https://blazor.radzen.com/playground/b4a001f4-f612-43e2-87d5-06779f197769

Screenshots / GIF
Attached GIF demonstrates the issue step by step.

**

Image

**
This behavior started after upgrading from Radzen.Blazor 7.1.6 to 8.4.1.

Originally created by @daniel-almeida-vfxplc on GitHub (Dec 22, 2025). **Description** When using RadzenDropDown with the parameter ClearSearchAfterSelection="true", the search input is cleared after selecting an item (as expected), but the filtering applied previously remains active when reopening the dropdown. **Versions** Radzen.Blazor: 8.4.1 (previously 7.1.6 without this issue) .NET: 10 Render mode: Blazor Server **Steps to reproduce** 1. Open the playground: https://blazor.radzen.com/playground/b4a001f4-f612-43e2-87d5-06779f197769 2. Expand the dropdown and type something in the search input. 3. Select one of the filtered options — the dropdown collapses (expected). 4. Reopen the dropdown: - The search input is empty (expected because ClearSearchAfterSelection is true). - However, the filtering is still applied based on the previous search value (unexpected). 5. Typing a new value or pressing backspace resets the filtering correctly. **Expected behavior** When reopening the dropdown, the search input should be empty and no filtering should be applied. **Actual behavior** The search input is cleared visually, but the filtering logic still uses the previous search value until the user types again. **Minimal reproduction** Playground link: [https://blazor.radzen.com/playground/b4a001f4-f612-43e2-87d5-06779f197769](https://blazor.radzen.com/docs/) **Screenshots / GIF** Attached GIF demonstrates the issue step by step. ** ![Image](https://github.com/user-attachments/assets/b3f82e56-0551-4369-8b2c-7a5055d0360e) ** This behavior started after upgrading from Radzen.Blazor 7.1.6 to 8.4.1.
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#1943
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?