Couldn't this be solved by acknowledging that there is application-domain state (such as the value of the text field) and UI state (such as the cursor position and selection), which can be represented by an application-domain model and view model respectively, rather than trying to pretend that the latter doesn't exist?

Although if you model all the UI state, maybe you just end up with the DOM?