Yes I would switch to the readonly attribute field for the full record, instead of variable input. Variables are useful for many purposes, but they increase complexity and I would generally avoid complexity wherever possible.
We avoided a 'closed form event' because our form management is quite complicated as is and there are many edge cases where it would be quite hard to explain when/if a form would be considered 'closed'. It´s also tricky, because we cannot always execute this event, as when for example, a user closes the browser. If your app relies on this event to update data or logs and the event is not always executed, your business logic may break.
The warning you see in the console log is normal if you are using a self-built version of r3 and did not optimize the web resources you deploy r3 with. In this case, vue.js (the UI framework we use for r3) is running the dev version instead of the production version. When we ship r3, we optimize the JS libraries on the release build. Are you running your own version of r3? If not, please let me know, which version of r3 you are running so that I can check if we failed to optimize the web resources there.
