clean up global event listener, when connection closed

[zuizuihao]

I found the ROOT CAUSE, @javiercn can we clean up the global event listener, when connection closed?
when Blazor connection closed, the detachWebRendererInterop in the callback of connection.onclose will be invoked. here, it will invoke interopMethodsByRenderer.delete(rendererId);, all the interopMethodsByRenderer will be cleaned. also There are lots of global event listener in form.js like window.addEventListener('focus'), window.addEventListener('keydown'). if user still interact with our app like focus, click, the global event will be triggered, then invoked EventDelegator.onGlobalEvent, invoked EventDelegator.dispatchGlobalEventToAllElements invoked WebRendererInteropMethods.dispatchEvent invoked WebRendererInteropMethods.getInteropMethods, here since the interopMethodsByRenderer is empty, will throw this exception.

Originally posted by @zuizuihao in #56813 (comment)

[javiercn]

@zuizuihao thanks for contacting us.

Does this happen when you use MapRazorComponents and blazor.web.js or are you still relying on MapRazorComponents with blazor.server.js.

[zuizuihao]

nope, now we totally migrated into ASP.Net 8 using web.js.
<script src="_framework/blazor.web.js?version=8"></script> in App.razor script body.
endpoints.MapRazorComponents().AddInteractiveServerRenderMode()

[lofcz]

This is a showstopper issue we also ran into, please consider upping the priority on resolving this given the call stack is already figured out.

[zuizuihao]

Hi @javiercn , I draft a PR for it to fix it, hope you can help us review it, we just don't want it to throw exception. when it's to be an exception will trigger different handle logic in our system.
#58667