MudBlazor/MudBlazor

MudForm.IsValid Defaults to `false` with Required Fields

Closed

#5,196 opened on Sep 1, 2022

View on GitHubContributor guide
 (9 comments) (3 reactions) (0 assignees)C# (1,631 forks)batch import
bughas workaroundhelp wanted

Repository metrics

Stars
 (10,394 stars)
PR merge metrics
 (Avg merge 6d 6h) (108 merged PRs in 30d)

Description

Bug type

Component

Component name

mudForm

What happened?

<MudForm Model="@_model" @ref="@_form" @bind-IsValid="@_success" Validation="@(_loginValidator.ValidateValue)"> .... @{ bool _success=true; } when mudform initialize not any change, I think this "_success" should not be change. right? but actually, the _success value always change to false, even _loginValidator return vaild( not any errors)

Expected behavior

I think IsValid does not change when mudform initializes.

Reproduction link

https://try.mudblazor.com/snippet/mamGEtEFuJcosnnE

Reproduction steps

<MudTextField @bind-Value="model.Name"
For="@(() => model.Name)" Immediate="true" Required="true" Label="Name" />

when Required="true", even default set value. ...

Relevant log output

No response

Version (bug)

6.xxx

Version (working)

No response

What browsers are you seeing the problem on?

Chrome

On what operating system are you experiencing the issue?

Windows

Pull Request

  • I would like to do a Pull Request

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributor guide

Research direction
Investigate the MudForm component's initialization of the IsValid property. Trace how required fields affect the initial validation state. Check if the validation runs on initial render causing IsValid to become false even with a valid model.
Tech stack
csharp
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Blazor
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70