Issue #5328πŸ’¬ AnsweredOpened August 22, 2023by sdimitrenco0 reactions

Editable text after remove focus of RTE, returns back previous state of content.

Quick answerby artf

You shouldn't have "content" inside your text span, indeed if you replace it with "components": "[email protected]", it will work properly.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome

Reproducible demo link

https://jsfiddle.net/sdimitrenco/wao1rh0q/30/

Describe the bug

That is my components struct

  {
    "type": "link",
    "components": [
      {
        "type": "image",
        "attributes": {
          "src": "http://localhost:8003/swt/upload/files/svg_images/envelope-square-solid.svg",
        }
      },
      {
        "tagName": "span",
        "type": "text",
        "content": "[email protected]",
      }
    ]
  }

If I change the text in the span tag in the text editor, then remove focus from that word, it returns the previous state of the text. The structure of the components looks normal, a link, but inside the picture and text inside the span tag.

DEMO image

LIVE https://jsfiddle.net/sdimitrenco/wao1rh0q/30/

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (2)

artfβ€’ August 25, 2023

You shouldn't have "content" inside your text span, indeed if you replace it with "components": "[email protected]", it will work properly.

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @sdimitrenco.

The issue with editable text after remove focus of RTE, returns back previous state of content. appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state.

What to try:

  1. Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
  // your operation here
}, 0);
  1. Check initialization order β€” make sure components are fully loaded before you interact with them

  2. Use the editor's event system β€” listen to completion events:

editor.on('component:mount', (component) => {
  // safe to interact with component here
});

Recommended next steps:

  • Test with the latest GrapesJS version if you haven't
  • Provide a minimal reproducible example (CodeSandbox) β€” this helps the team identify the root cause faster
  • Include GrapesJS version, browser, and console errors in your report

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins β†’
Premium option

Premium plugins ship with support, regular updates, and production-ready features β€” save days of integration work.

Browse premium plugins β†’

Related tutorials

In-depth guides on the same topic.

All tutorials β†’

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.