VERNOU Cédric
VERNOU Cédric
Actually, `MudButtonGroup.FullWidth` stretches the group, but not the buttons :  The modification can be, `MudButtonGroup.FullWidth` forces `MudButton.FullWidth` on children :  Except if one or many children have explicit...
@ScarletKuro, @danielchalmers, do you think it need to manage other type of button? Here are all the button types I have identified: - MudButton - MudFab - MudIconButton - MudToggleIconButton...
@danielchalmers, if the button group is stretched and contains only other button type, then the available space will not be filled. Example : ```razor ``` 
@henon From what I understand, `MudButtonGroup` need to stretch `MudButton`, `MudIconButton` and `MudToggleIconButton`, but not `MudFab`. Currently, `MudIconButton` and `MudToggleIconButton` don't support stretch, so first we need to add it....
`MudForm` at start ([OnAfterRenderAsync](https://github.com/MudBlazor/MudBlazor/blob/f3170833e41a52c3fcd3981bbf20402c42900d26/src/MudBlazor/Components/Form/MudForm.razor.cs#L337)) take the valid state if none field is required, but don't do a complete validation. The validation is executed only after a user interaction. @ScarletKuro ,...
`MudAutocomplete` has this comment in the method [`OnInputBlurredAsync`](https://github.com/MudBlazor/MudBlazor/blob/fe057460e7ff3753343f2434d27e1ed6ae34fd12/src/MudBlazor/Components/Autocomplete/MudAutocomplete.razor.cs#L937) : > we should not validate on blur in autocomplete, because the user needs to click out of the input to select...
You can manually force the validation on autocomplete blur like : ```razor @code { MudForm form; private void ForceValidation() { form?.Validate(); } // ... } ``` See this example :...
[The value is coerced only if the search return 0 element](https://github.com/MudBlazor/MudBlazor/blob/ed81ebe4ed5e66de771c574e080e2168de7941f0/src/MudBlazor/Components/Autocomplete/MudAutocomplete.razor.cs#L717), so the value is coerced after search, so after the debounce interval. But some event like OnBlur stop the...
Associated to #9874. The bug is partially fixed by the PR #9881. When `Immediate` is disable, the value is coerced on blur. But the problem persists when `Immediate` is enable....