[BUG] ModuleMessage Throws Exception in Static Render Mode For Static Components

[sbwalker]

Oqtane Info

Version - 5.1.1
Render Mode - Static
Interactivity - Server
Database - SQL Server

Describe the bug

When a module component is using Static render mode, the AddModuleMessage() can be used to display a message to a user. However when a user clicks the X icon to close the message, an error will be produced in the browser similar to the following:

Cannot submit the form 'ModuleMessageForm33' because no form on the page currently has that name.

If you look at the HTML markup of the page prior to clicking the X icon, it appears that the form does exist:

Expected Behavior

The message should be closed and no error should occur.

Steps To Reproduce

Anything else?

I believe Blazor may be removing the form element from the DOM before the onsubmit event is fired? Or perhaps the elementreferences in the ModuleMessage component are causing issues.

A secondary issue is that the RenderModeBoundary is creating 2 ModuleMessage components regardless of whether a message needs to be displayed or not. This adds a lot of extra components to a page which is contrary to the performance goals of Oqtane. It would be preferable if ModuleMessage components are only added when a message needs to be displayed.