The changesCount parameter should be reset to zero when we undo the images

Hi! @marcepoblet can you please share the part of the code which you used to define the changesCount variable to get it incremented?

Closing this as I don't see any substantial benefit for this functionality

Thanks for reporting this, @marcepoblet.

The issue with The changesCount parameter should be reset to zero when we undo the images 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);

2. Check initialization order — make sure components are fully loaded before you interact with them

3. 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