Blocks break apart unexpectedly when text contains tabs about lexical HOT 4 CLOSED

To be clear, I don't think that the presence of a tab should spawn a new block (edit: text node) at all.

from lexical.

@steveluscher please could you also paste in the step recorder output test case? Might as well use it given we have it!

from lexical.

{
  name: '<YOUR TEST NAME>',
  inputs: [
    insertText("v"),
    moveNativeSelection([0,0,0],2,[0,0,0],2),
    insertText("C"),
    deleteWordForward()
  ],
  expectedHTML: '<div contenteditable="true" data-outline-editor="true"><p class="editor-paragraph" dir="ltr"><span>ABC</span><span></span><span>EFG</span></p></div>',
  expectedSelection: {
    anchorPath: [0,1,0],
    anchorOffset: 0,
    focusPath: [0,1,0],
    focusOffset: 0,
  },
},

The insertText("v") isn't really accurate. That was the clipboard paste. You can file that as another bug if you like :)

The problem is that you can't type tabs in the example app. I have to paste.

from lexical.

Looks like the reason we split up the text node into multiple blocks on the first paste is because of the useMentions hook. As there are capital letters, it prepares the text for potentially needing to be a mention. The reason it happens again is because of the useMentions plugin again, applying a split. I'll look into how the plugin can undo it's split when it detects no results :)

from lexical.