Sergey Kolemasov

Bumped into same problem. In my case I was using Fluid.Core 2.9 package in another part of my application. This caused issues with Liquid Renderer. I assume that there was...

My guess is that Blazor recycles the deleted component and uses it again. As far as I can see MudFormComponent doesn't update error state on [parameters set](https://github.com/MudBlazor/MudBlazor/blob/a7d99775ec517bcedd68241500a405122985b052/src/MudBlazor/Base/MudFormComponent.cs#L714).

Hello team, This bug is still present in the latest MudBlazor version. It is not a cosmetic or non-important issue. This renders MudBlazor built-in form validation useless in any scenarios...

Here you go: https://github.com/user-attachments/assets/e6a92d4e-7a2a-4c33-86f3-dc47e08a3f3b Please note the control in the mode that allows new values, so it should not reset to empty. Here is an example, of the value reset,...

It works okay on 6.19.1. Also I believe it worked fine on other prior 6.x versions too.

I am using WASM. Honestly, I saw glitches like ignoring some characters typed before with longer DebounceInterval in 6.x as well. And I had to reduce it to minimize chances...