Blur event inside form can cause "no event handler associated with this event" exception

[SteveSandersonMS]

Scenario:

<EditForm OnValidSubmit="NavigateToAnotherPage">
    <input @blur="@(() => {})" />
</EditForm>

Pressing "enter" inside the input causes:

System.ArgumentException: There is no event handler associated with this event. EventId: '45'.
Parameter name: eventHandlerId
  at Microsoft.AspNetCore.Components.RenderTree.Renderer.DispatchEventAsync (:44300/System.UInt64 eventHandlerId, Microsoft.AspNetCore.Components.RenderTree.EventFieldInfo fieldInfo, System.EventArgs eventArgs) <0x3124c68 + 0x00054> in <filename unknown>:0 
  at Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer.DispatchEventAsync (:44300/System.UInt64 eventHandlerId, Microsoft.AspNetCore.Components.RenderTree.EventFieldInfo eventFieldInfo, System.EventArgs eventArgs) <0x31248a0 + 0x00078> in <filename unknown>:0 
  at :44300/Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer.ProcessNextDeferredEventAsync () <0x3477c48 + 0x000a6> in <filename unknown>:0 
    at Object.endInvokeDotNetFromJS (blazor.webassembly.js:1)
    at Object.invokeJSFromDotNet (blazor.webassembly.js:1)

Looks like the "navigate away" gets processed before the "blur", so the component has been disposed by the time we process its "blur" event handler.

[MichaelKueh]

@SteveSandersonMS are there any plans to include this to release 3.2?

[SteveSandersonMS]

Sorry, the deadline for that has already passed. We're really close to the 3.2 release now!

[jameschch]

EDIT: It's not unusual to receive a similar error to this for various events:

blazor.webassembly.js:1 Uncaught (in promise) Error: System.ArgumentException: There is no event handler associated with this event. EventId: '8'.

This can be caused by an error during render which means the element was bound to an event but the error prevented instantiation of the handler.

[jespersh]

I tried playing with this call before NavigateTo

await JSRuntime.InvokeVoidAsync("document.activeElement.blur");

but it only worked the first time I saved my form

[vstribrny]

Please notice there's the same issue also with onfocusout event. I am also facing this issue. The onblur and onfocusout are basically unusable because you never know when user navigates back...

@SteveSandersonMS
Is there a chance to include a fix into some patch for 3.2?

[ghost]

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[mkArtakMSFT]

@captainsafia the contenteditable issue may be related to this one. Please start from this one. If it is the same cause - great. If not, the other issue may need to be pushed out as it doesn't seem very critical.