Currently, if a selection event happens after an edit event (even if it's really far from the edit), then the selection event will be combined into the edit event when being re-done. This causes a redo to scroll the document to a different place in the document, where the changes applied by the redo would be possibly out of view.
I would argue that when re-doing, users expect the cursor to be put immediately where the edit happened, rather than somewhere else.
In this demonstration, I type some letters, click at the end of the file, then attempt to undo, then redo.
Expected: See the text that was re-done.
Actual: Can't see it because I was scrolled to the end.
The text was updated successfully, but these errors were encountered:
Currently, if a selection event happens after an edit event (even if it's really far from the edit), then the selection event will be combined into the edit event when being re-done. This causes a redo to scroll the document to a different place in the document, where the changes applied by the redo would be possibly out of view.
I would argue that when re-doing, users expect the cursor to be put immediately where the edit happened, rather than somewhere else.
In this demonstration, I type some letters, click at the end of the file, then attempt to undo, then redo.

Expected: See the text that was re-done.
Actual: Can't see it because I was scrolled to the end.
The text was updated successfully, but these errors were encountered: