Issue—Blazor ValueChanged event did not fire with built-in input elements
Yes, this is a known issue in Blazor. You can track the issue link in the ValueChanged event not fired thread. The following code snippet will work. You have to update the model manually because handling the ValueChanged event does not let you use the @bind-Value we need to use ValueExpression instead of @bind-Value. Instead, you can also use the OnValidSubmit form event to get and process the value.
What if the component ref/instance is not working? Or the component ref is undefined?
The component instance filed is populated along with the component after rendering completion. You must access the component instance in the OnAfterRenderAsync or OnAfterRender methods of the Blazor lifecycle.
Issue—Blazor: IJSRuntime.InvokeAsync serialization broken for arrays of objects.
The InvokeAsync accepts only params object[] args, so the array of objects is parsed as a single, top-level entry in args. You have to pass the array of objects as a single object by casting. The following code only passes the single array object. [JS helper] [Razor] By casting the array into an object, it retrieves all the values. Refer to the following link for more information. https://github.com/aspnet/AspNetCore/issues/8743
How do I get the reference or instance of a component?
Component references are used to invoke methods from underlying components. Use the ref attribute for a component and define it filed with the same name and same type of component. While the Counter component is rendered, the field counter is populated along with the component instance. For more information, refer to the link capture-references-to-components.
Does Blazor have to always show dates in UTC format?
This is a known issue with Mono Runtime when Blazor runs on client. Issue tracker: WebAssembly: Missing Timezone implementation As a workaround, you can use the library Toolbelt.Blazor.TimeZoneKit.