WARNING - Malfunction: After using the Flexmonster component on the Chrome browser it is no longer possible to fill input fields with autocomplete set to 'on'.

After using the Flexmonster component on the Chrome browser,
it is no longer possible to fill input fields with autocomplete set to 'on'.
Environment: .NET Core MVC/Ajax application.
The following outlines the scenario that leads to the horror.

In image 1, we are at the startup of the application without ever having loaded a page containing the Flexmonster component.
In image 2, we open a data entry page where we use the input field autofill by selecting from Chrome's autocomplete list.
As shown in figure 3, after successfully saving the data, we go to the menu on the left to open a page containing the Flexmonster component.
After opening the page with the Flexmonster component, we return to the previous page to enter new data
As soon as we try to fill in the input field using an item from the autocomplete list, an error occurs, see figures 4 and 5.
This issue doesn't seem to occur in Firefox, but our reference browser is Chrome.
It SEEMS that the component registers as an observable on some event and then remains active, compromising the functionality of the autocomplete.