You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
I have read the documentation and cannot find an answer.
Describe the bug
If two or more instances of the editor are used and content has been created in them, when undo/redo is called in one editor, undo/redo is also performed in the other editors when all changes have been completed in the current editor.
Undo/redo all changes in one of them and keep doing undo/redo (either with shortcut or with the button in the toolbar)
See undo/redo applied to the other editor as well
Expected behavior
Undo/redo only applies to the content of the editor, where it was called.
Video
2024-07-24.23-32-15.mp4
Desktop
OS: Windows
Browser: Chrome
Stack: Next.js App-Router
Additional context
I went back to version 2.0 and the error still occurred. Only when I switched to version 1.* did undo/redo only apply to the content of the editor to which it belongs.
The text was updated successfully, but these errors were encountered:
If you want to ask for support or request features, sponsor the project and contact me over email.
Describe the bug
If two or more instances of the editor are used and content has been created in them, when undo/redo is called in one editor, undo/redo is also performed in the other editors when all changes have been completed in the current editor.
Reproduction
https://codesandbox.io/p/sandbox/mdx-editor-base-forked-r7vynx
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Undo/redo only applies to the content of the editor, where it was called.
Video
2024-07-24.23-32-15.mp4
Desktop
Additional context
I went back to version 2.0 and the error still occurred. Only when I switched to version 1.* did undo/redo only apply to the content of the editor to which it belongs.
The text was updated successfully, but these errors were encountered: