The source of the issue was with your Template components containing iFrames.

The Template components were associated a Model on your page that was being changed a lot, and the way the Template component works is that any time you make a change to any field on the Template’s source Model, then all Template components bound to this Model will dynamically update / rerender. Therefore your iFrames are being rerendered, and elements on the iFrame are stealing focus away from the field the user is typing into.

All you have to do to fix this is to change the Model associated with your Template components to be some other Model that is not getting live-updated all the time. What I did for your original scenario was to create a dummy model called “RunningUser” that only pulls in the User Id of the current user — since this Model is never going to change or be updated. I then associated all of your Template components with this RunningUser model. This strategy could work for other pages as well. You don’t necessarily need to create a dummy model, you could use some other Model that is never going to have changes, but a dummy model will guarantee that the templates will never live-update and cause the problem you were having.

Then, you can use replace any references to fields in your original Model with either $Model or $Param global merge variables, with triple-braces to ensure that these merges are never live-updated.

For example if you had a Template previously bound to an “Account” model’s Id field like this:

You could replace the {{Id}} merge with {{{$Param.id}}} or {{{$Model.Account.data.0.Id}}}

I thought there was another forum post about this issue,  but I cannot find it.   Check throughout your page to ensure that any template components that wrap iFrames are not connected to the same model that your field editor is also connected to.  What is happening is that as you start typing in the field the iFrame detects a change in the model and attempts to rerender.  When the re-render happens the focus is moved from the field to the iFrame and you get the weird page behavior. 

You should first try to turn off the “Enable HTML” property.  If that does not work (or causes other problems)  build a second model that is only connected to the Template.  It would only need to have the data necessary for inclusion in the iFrame (probably the ID for the object). 

Hope that helps. 

You dudes are great.  Thanks for the help, i think this is what John had done last time we had the issue.  Now at least its on the board with an easy fix.  Keep it krakan!!