Issue—System.InvalidOperationException: Object of type ‘Microsoft.AspNetCore.Components.Forms.InputText’ does not have a property matching the name ‘type’.
As of now, there is no support for including arbitrary attribute support for the built-in input component <InputText />. You have to remove the type attribute to resolve this issue. There is a plan for including the type=”password” attribute for the <InputText> component, which can be tracked in this GitHub thread. [Issue Resolved]
I could not find the property of window when calling the JavaScript method in Blazor using JS interop.
You have to refer to the JavaScript method implemented JS (external-script.js) file in index.html properly and then call the function from .NET using IJSRuntime. [wwwroot/index.html] [wwwroot/external-script.js] [Pages/Index.razor]
How do you use the invoke method on a parameter value change?
The better solution is to invoke the method in the set value of the parameter. You can also override the OnParameterSet or OnParameterSetAsync lifecycle methods. Those methods are triggered every time any parameter value changes.
What if I am unable to use or validate the password type input text in a Blazor form?
For now, there is no password-type built-in input component. You can track the availability of <InputText type=”password” /> in this thread. [Issue Resolved]
Is it safe to include passwords in client-side WASM code?
No, the WASM codes can be decompiled. Use this WebAssembly to C decompiler.