Repository navigation
MudInput: Avoid duplicate blur interop during normal focus changes - #13049
Merged
Merged
Conversation
…ck cases This fixes a `MudTextField` / `MudButton` race where clicking a button immediately after editing a non-`Immediate` text field could execute the button `OnClick` before the field value was committed. Root cause: `MudInput` had two independent blur paths: - the normal Blazor `@onblur` handler - a JS blur bridge added in `MudBlazor#10842` that called back into `.NET` separately That extra JS interop path could bypass Blazor’s normal ordered `change -> blur -> click` processing and create intermittent stale model values, especially on Blazor Server. What changed: - keep native Blazor blur as the primary path - treat the JS blur bridge as a fallback only - skip the JS callback when focus moves normally to another element - dedupe native blur and JS fallback so the same blur is only processed once - add regression coverage for duplicate blur delivery This keeps the fix platform-agnostic instead of relying on an iOS-only device check, while still preserving a fallback for cases where focus is dismissed without Blazor observing a native blur.
mudbot
Bot
added
the
bug
danielchalmers
changed the title
This was referenced Apr 22, 2026
This was referenced Sep 17, 2026
This was referenced Sep 28, 2026
This was referenced Oct 8, 2026
This was referenced Oct 15, 2026
This was referenced Oct 23, 2026
Merged
3 tasks done
vantaflow
added a commit
to vantaflow/MudBlazor
that referenced
this pull request
Nov 1, 2026
MudMask re-applies the caret after every render while _isFocused is true, and the JS selectRange helper always calls element.focus(). When the native blur is not delivered (e.g. Hybrid hosts losing window focus), _isFocused stays true and each render steals focus back from other inputs. Add the JS blur fallback bridge that MudInput already uses (MudBlazor#10842, MudBlazor#13049) so the focus state is cleared even without the native blur event.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This fixes #13011, a
MudTextField/MudButtonrace where clicking a button immediately after editing a non-Immediatetext field could execute the buttonOnClickbefore the field value was committed.Root cause:
MudInputhad two independent blur paths:@onblurhandler.NETseparatelyThat extra JS interop path could bypass Blazor’s normal ordered
change -> blur -> clickprocessing and create intermittent stale model values, especially on Blazor Server.What changed:
This keeps the fix platform-agnostic instead of relying on an iOS-only device check (closes #13047), while still preserving a fallback for cases where focus is dismissed without Blazor observing a native blur.
Checklist: