I inserted a showmessage before and after each key-hit. It shows the position the same at before and after, and advanced for the next key.
What shows as the cursor position, however, is cursor to the right then cursor to left, again right, then again left, etc. It does not matter what order the keys are hit. So it isn't the key typed, nor is it selstart. What happens by code is not what you see on the screen.
Additionally what is saved the correct typing order, but it is not the natural unicode values for the keys. Each key is preceded with a \u-10238?, and then a key code... for $10900 it is \u-8953?, then for $10901 it is \u-8955? ...they have the "\u-" prefix (which is something that have never seen, and as well, I have never seen a \u-10238? as a leader for each key) and they are jumping by incrementing 2's .
\par
\f0\fs20\u-10238?\u-8953?\u-10238?\u-8955?\u-10238?\u-8957?\u-10238?\u-8959?\u-10238?\u-8960?\u-10238?\u-8958?\u-10238?\u-8956?\u-10238?\u-8954?\par
All of this is with the NotoSansPhoenician-Regular font.
Rick