Migrates MudBaseInput.Value to use ParameterState pattern, consistent with previous Text migration (#12259).

Changes

MudBaseInput

• Value ParameterState: Registered _valueState with change handler OnValueParameterChangedAsync
• TextUpdateSuppression logic: Moved from SetParametersAsync to OnValueParameterChangedAsync to properly handle value-to-text synchronization with focus/suppression checks
• Text/Value conflict prevention: Uses ParameterView.TryGetValue() in change handlers to detect when both Text and Value are present in the same parameter update (maintains hasValue && !hasText semantics)
• SetParametersAsync preservation: Kept the hasValue && !hasText logic in SetParametersAsync to handle cases where Value parameter is passed unchanged (needed for text formatting)
• ForceUpdate fix: Manually invoke ValueChanged callback when value hasn't changed but force: true (ParameterState doesn't fire callbacks for unchanged values)
• ReadValue/WriteValue overrides: Use _valueState.Value and _valueState.SetValueAsync() instead of backing field

MudColorPicker Text/Value Synchronization Refactoring

• TextField binding: Changed from computed value @GetColorTextValue(_valueState.Value) to _textState.Value to enable Blazor parameter change detection
• ColorPickerMode change handler: Added OnColorPickerModeChangedAsync to update Text when display mode changes (RGB → HSL → HEX)
• Initial Text synchronization: Text is initialized when Value is first set in OnValueChangeHandlerAsync
• Invalid input handling: When color parsing fails, _textState.SetValueAsync() is called to reset Text, which triggers TextField to receive updated parameter and reset its display
• Root cause fix: Solves the core issue where Blazor doesn't pass unchanged parameters - by updating _textState, we force Blazor to pass the Text parameter to TextField, enabling proper reset on invalid input

Test Results

• ✅ TextField_TextUpdateSuppression - Fixed
• ✅ Select_ValueChangeEventCountTest - Fixed
• ✅ SetColorInput_InvalidNoChange - Fixed
• ✅ NumericFieldTestCultureFormat - Fixed (regression introduced and resolved)

Architecture Improvements

ParameterView-Based Conflict Detection

Eliminated the _textParameterChanged flag by using ParameterView.TryGetValue() within change handlers. Each ParameterChangedEventArgs now includes a snapshot of the ParameterView, allowing handlers to check if other related parameters are also present in the same update. This approach is thread-safe by design and eliminates the need for manual flag management or atomic operations.

Two-Way Binding Edge Case

The refactoring addresses two critical edge cases in two-way binding scenarios:

1. ColorPicker invalid input: When TextField receives invalid input and ColorPicker's parsing fails, the TextField's Value prop doesn't change, so Blazor doesn't pass it as a parameter. By switching to _textState.Value binding and keeping Text synchronized with Value through ParameterState change handlers, TextField now properly receives parameter updates and resets its display.
2. NumericField formatting: When Value is set internally and passed back through two-way binding with the same value, Blazor doesn't pass it as a parameter. The SetParametersAsync logic ensures Text is updated from Value even when Value parameter is present but unchanged, enabling proper formatting.

Checklist:

• I've read the contribution guidelines
• My code follows the style of this project
• I've added or updated relevant unit tests

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.