Ok - tested 14.1beta on MacOS and my iPadPro + Magic Keyboard. It’s … better … . It usually goes to the start of the line now with Cmd-Left, but not always, but there’s still something funky up with where it thinks the cursor is. I have a line of text that looks like this (hard returns below to show how it looks on my machines):
Want to talk about what’s next for him but last we talked about it he asked that we discuss that
later in the year.
Cmd-Left seems to work as expected, but if I put the cursor on the line above this one and hit the down arrow (no Cmd) it properly moves the cursor to before the “W” but if I hit the down arrow again, it goes to the end of that line - meaning it puts the cursor after the “t” in “that”. Down arrow again properly puts the cursor before the “l” in later. This seems to happen on all wrapped lines. Up arrow movement seems to do the same thing when starting in the left most position of a line below a wrapped line and hitting up - you end up at the end of the first part of the wrapped line. Meaning if I was in the first position of the line after the above text and hit the up arrow, the cursor would end up after the “t” in “that”, not before the “l” in later.
I hope that makes sense - if you want me to capture video of this or anything, yell. Thanks again! — Dan