Issue #6587πŸ’¬ AnsweredOpened August 13, 2025by Sebbones0 reactions

Adding text to a symbol replaces the text node over and over again

Quick answerby ClaudeCode

Thanks for reporting this, @Sebbones. Great question about Adding text to a symbol replaces the text node over and over again. The recommended approach with Components is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific module Look for the on() event listener method Most oper...

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Firefox Developer 142.0b9, Chrome 138.0.7204.184

Reproducible demo link

https://jsfiddle.net/artur_arseniev/ta19s6go/

Describe the bug

How to reproduce the bug?

  1. Make the "Article" component a symbol
  2. Add a text component to the original "Article" component
  3. Directly try to edit the text or set the cursor inside the text

What is the expected behavior? Cursor is not always resetting to position 0 and the text component is not flickering, behaving like a normal text component.

What is the current behavior?

  • The cursor is reset to position 0 and its almost impossible to select text
  • Constant editor 'component:add' events are fired

After "leaving" the text component and re-selecting it, the problem is gone and no further component:add events are fired. I think for some reason the newly created text component is constantly replaced it with itself.

I haven't had the time to look into the code yet, so currently no idea what could cause the issue.

If anything is missing or unclear, please let me know. Have a nice day :)

Code of Conduct

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

Answers (1)

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @Sebbones.

Great question about Adding text to a symbol replaces the text node over and over again. The recommended approach with Components is to use the event-driven API.

Start here:

  1. Check the GrapesJS documentation for your specific module
  2. Look for the on() event listener method
  3. Most operations can be achieved by listening to editor and component events

Common patterns:

// Listen for changes
editor.on('change', () => console.log('something changed'));

// Component lifecycle
editor.on('component:mount', (c) => console.log('component ready', c));
editor.on('component:update', (c) => console.log('component updated', c));

If you're still stuck:

  • Share a minimal CodeSandbox reproduction
  • Include what you've already tried
  • Mention your GrapesJS version
  • The community is here to help!

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.