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

[PR #2362] [CLOSED] Textbox/TextArea : add debounce parameter to make Immediate easier on the UI Thread #3217

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

📋 Pull Request Information

Original PR: https://github.com/radzenhq/radzen-blazor/pull/2362
Author: @joriverm
Created: 11/20/2025
Status: ❌ Closed

Base: master ← Head: fixes/textboxDebounce

📝 Commits (1)

  • 822eb8b Textbox/TextArea : add debounce parameter to make Immediate easier on the UI thread

📊 Changes

4 files changed (+82 additions, -10 deletions)

View changed files

📝 Radzen.Blazor/RadzenTextArea.razor (+4 -4)
📝 Radzen.Blazor/RadzenTextArea.razor.cs (+37 -1)
📝 Radzen.Blazor/RadzenTextBox.razor (+1 -1)
📝 Radzen.Blazor/RadzenTextBox.razor.cs (+40 -4)

📄 Description

We noticed that when using immediate if you would type faster than it takes to process the input & re-render it will start acting weird. some text is removed, input shows up delayed, drops some letters being typed etc etc.

Sadly this only happens if the UI is very busy/has a lot of controls etc etc so its very hard to reproduce -_-
I used the existing debounce classes to delay the processing of the input, but only if the delay is given which is 0 by default so it behaves as before.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/radzenhq/radzen-blazor/pull/2362 **Author:** [@joriverm](https://github.com/joriverm) **Created:** 11/20/2025 **Status:** ❌ Closed **Base:** `master` ← **Head:** `fixes/textboxDebounce` --- ### 📝 Commits (1) - [`822eb8b`](https://github.com/radzenhq/radzen-blazor/commit/822eb8b1f7719a38039b4f6905b0d0c68fe863c8) Textbox/TextArea : add debounce parameter to make Immediate easier on the UI thread ### 📊 Changes **4 files changed** (+82 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `Radzen.Blazor/RadzenTextArea.razor` (+4 -4) 📝 `Radzen.Blazor/RadzenTextArea.razor.cs` (+37 -1) 📝 `Radzen.Blazor/RadzenTextBox.razor` (+1 -1) 📝 `Radzen.Blazor/RadzenTextBox.razor.cs` (+40 -4) </details> ### 📄 Description We noticed that when using immediate if you would type faster than it takes to process the input & re-render it will start acting weird. some text is removed, input shows up delayed, drops some letters being typed etc etc. Sadly this only happens if the UI is very busy/has a lot of controls etc etc so its very hard to reproduce -_- I used the existing debounce classes to delay the processing of the input, but only if the delay is given which is 0 by default so it behaves as before. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
claunia added the pull-request label 2026-01-29 18:22:28 +00:00
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 pull-request
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#3217
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?