Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Deletion of an inline node is not working if it is immediately followed by an inline atom node #5920

Open
1 task done
joulev opened this issue Dec 7, 2024 · 0 comments
Labels
Category: Open Source The issue or pull reuqest is related to the open source packages of Tiptap. Type: Bug The issue or pullrequest is related to a bug

Comments

@joulev
Copy link

joulev commented Dec 7, 2024

Affected Packages

core

Version(s)

2.10.3

Bug Description

When an inline node is followed by an inline atom node, deletion is not working properly.

In the CodeSandbox URL provided below, on each line, go to the end of the line, then keep deleting.

  • Line 1: Characters are deleted one by one, which is correct

  • Line 2: "Ext2" (the atom node) is deleted in one go, other characters are deleted one by one, which is also correct.

  • Line 3: "Ext2" is still deleted in one go (correct), but "Ext1" is also deleted in one go (not correct).

Browser Used

Safari

Code Example URL

https://codesandbox.io/s/suspicious-cori-2kd4zq

Expected Behavior

In Line 3, after "Ext2" is deleted in one go, "Ext1" should be deleted character-by-character because Ext1 is not an atom node.

Additional Context (Optional)

No response

Dependency Updates

  • Yes, I've updated all my dependencies.
@joulev joulev added Category: Open Source The issue or pull reuqest is related to the open source packages of Tiptap. Type: Bug The issue or pullrequest is related to a bug labels Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Open Source The issue or pull reuqest is related to the open source packages of Tiptap. Type: Bug The issue or pullrequest is related to a bug
Projects
None yet
Development

No branches or pull requests

1 participant