Unresponsive Lexical UI bug

[rare frost]

Not quite sure what is causing this behaviour.
When adding an upload Block to Lexical it causes the UI to become unresponsive.

There are no errors.
I attached a screen capture of the issue

[surreal dagger]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• Converting Markdown - Converting MDX - Defining a Custom Block
• Converting JSX - Richtext to JSX - Lexical Blocks
• Converting HTML - Blocks to HTML
• React Hooks - useDocumentForm
• Blocks Field - Block Field - Admin Options - Customizing the way your block is rendered in Lexical

[ocean kite]

Hey @rare frost could you provide a couple of things:

• What version of payload
• using a specific payload template
• can you share your field config that sets up lexical if you did this from scratch

[rare frost]

"payload": "^3.79.0", I believe I used the multitenant template -

  editor: lexicalEditor({
    admin: {
      hideGutter: true,
    },
    features: (props) => {
      return [
        ...props.defaultFeatures,
        FixedToolbarFeature(),
        BlocksFeature({
          inlineBlocks: richTextBlockList.inline,
          blocks: richTextBlockList.blocks,
        }),
        TextStateFeature({
          state: textStateValues
        }),
      ]
    },
  }),

Bear in mind that I updated from I believe payload@3.55.0 to try and fix this

[ocean kite]

can you open the inspector and see what the console is throwing for errors?

I've got to imagine it is lighting up like a christmas tree if something like this is happening

[rare frost]

Just double checked, there is no error

I do remember its a local only problem though

[ocean kite]

no errors in the terminal either?

[rare frost]

nothing at all

some incorrect form label issues buts thats been there for as long as I can remember

[ocean kite]

hmm very strange! I will try to reproduce

[rare frost]

It is, but since its only locally it seemingly isnt the biggest problem