# Unexpected cursor position after redo

**URL:** <https://discuss.prosemirror.net/t/unexpected-cursor-position-after-redo/9145>\
**Category:** Uncategorized\
**Created:** [November 18, 2026, 5:25pm UTC](https://discuss.prosemirror.net/t/unexpected-cursor-position-after-redo/9145 "2026-11-18T17:25:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![5v37](https://discuss.prosemirror.net/user_avatar/discuss.prosemirror.net/5v37/32/4570_2.png) [@5v37](https://discuss.prosemirror.net/u/5v37)\
**Post date:** [November 18, 2026, 5:25pm UTC](https://discuss.prosemirror.net/t/unexpected-cursor-position-after-redo/9145/1 "2026-11-18T17:25:42Z")

</div>

I’ve noticed some counterintuitive cursor behavior when undoing and redoing edits made in different parts of a document.

For example, if you type `"X"` at the start of a paragraph, move the cursor to the end and type `"Y"`, then press `undo` twice and `redo` once — `"X"` is restored at the start, but the cursor jumps to the end of the paragraph (where `"Y"` will be restored on the next `redo`), instead of staying right after `"X"`.

In most editors, `undo` and `redo` are symmetrical: `undo` puts the cursor at the selection before the change, while `redo` puts it right after the restored text, where you left off after making that edit.

Is this considered a bug in `prosemirror-history` that can/should be fixed, or is it an intentional trade-off in the history model that needs to be worked around at the application/plugin level?
