Issue #6087πŸ’¬ AnsweredOpened August 24, 2024by leo-budgetsimple1 reactions

Undo doesn't work after a Component's innerHTML is changed

Quick answerby artf❀ 1

UndoManager tracks component state changes, not its DOM. This should work in your case element.components('Hello Planet')

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Latest

Reproducible demo link

https://jsfiddle.net/condsjm1/

Describe the bug

How to reproduce the bug?

  1. Change a Component's innerHTML
  2. Press CTRL + Z

What is the expected behavior? To undo the content

What is the current behavior? Doesn't undo the content

Description:

On the fiddle, press the button that says 'Change to Hello Planet' and then select the editor and press CTRL + Z

and the undo won't work (nor the redo), but if you change the 'Hello World' text normally it works fine.

I think I'm changing the content wrong? and if so what's the best way to change a component's content and emulate the native behaviour

Code of Conduct

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

Answers (3)

artfβ€’ August 25, 2024

UndoManager tracks component state changes, not its DOM. This should work in your case element.components('Hello Planet')

leo-budgetsimpleβ€’ August 25, 2024

@artf Thanks!

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @leo-budgetsimple.

Great question about Undo doesn't work after a Component's innerHTML is changed. The recommended approach with UndoManager 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.