Issue #5650πŸ’¬ AnsweredOpened January 29, 2024by Wayne-Mather0 reactions

When inserting text when component not synced, the text is overwritten from the existing model

Quick answerby artf

This is not a bug, merging the current DOM with components requires a bit more effort. There is already a similar API you can use or re-implement with your own needs (using component definition instead of HTML string)

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Edge 121.0.2277.83, Firefox 122

Reproducible demo link

https://jsfiddle.net/50mga1t7/1/

Describe the bug

How to reproduce the bug?

  1. Create a toolbar action to insert some text
  2. Edit a text node and insert some text
  3. Click the toolbar command to insert some new component/text
  4. The textnode will reset to the model details before the edit's took place

What is the expected behavior? The textnode should show the current text as being edited and the new inserted text

What is the current behavior? The new text is inserted using the text from the model rather than the current view

Code of Conduct

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

Answers (2)

artfβ€’ February 10, 2024

This is not a bug, merging the current DOM with components requires a bit more effort. There is already a similar API you can use or re-implement with your own needs (using component definition instead of HTML string)

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @Wayne-Mather.

Great question about When inserting text when component not synced, the text is overwritten from the existing model. The recommended approach with ProseMirror 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.