Editor not restore the selection state after update value

[akaguny]

Reproduce example link: https://codesandbox.io/p/sandbox/react-codemirror-example-codemirror-6-forked-sj8ynr
Reproduce:

1. open the example link
2. select unmodified content or select all content (important: after update selection should not to be collapsed)
3. click to the update content button

expected result: Editor selection restored
alternative expected result: Editor selection and browser selection not showed

actual result:

1. Editor selection now showed
2. Browser selection exist (green color of the text for demonstration)

demonstration:

editor.webm

workaround:
clear browser selection state before update editor state:

    const selection = window.getSelection();
    const range = selection?.getRangeAt(0);
    range?.collapse(true);

use collapse https://developer.mozilla.org/en-US/docs/Web/API/Selection/collapse as more safe way either empty https://developer.mozilla.org/en-US/docs/Web/API/Selection/empty

[Duo-Huang]

After the value changes, the cursor movement can no longer be listened by the EditorView.updateListener, resulting in the inability to update the cursor position and selection. I think the update of the value destroys the responsiveness of the EditorState https://codemirror.net/docs/ref/#state

[Duo-Huang]

In the case of uncontrolled components, whenever the input changes, or any behavior that changes the cursor position, the editorState instance will be regenerated. As the documentation says, editorState is an immutable object.

But under the controlled component, there is a strange problem after updating the value once. When the value continues to change, zustand can subscribe to the new state via const editorState = useStore((state) => state.editor.cmView?.state) (ref this https://codemirror.net/docs/ref/#view.EditorViewConfig.state). so I can get the new cursor position and select range base on it, but the strange thing happened codeMirror api updateListener cannot listen for state changes, I'm curious about what editorState has experienced under controlled components that lead to this difference