`getDirtyCount()` returns `1` after loading

Hi @padcom this is an expected behavior as the load itself updates the state of the editor. You can simply clear the dirty counter via editor.clearDirtyCount() right after your manual load.

Please note, that if you enable autoload:

    storageManager: {
      type: 'example',
      autoload: true,
      autosave: false,
    },

and disable loading:

  // console.log('App.vue - before load', editor.getDirtyCount())
  // const result = await editor.load({})
  // console.log('App.vue - after load', editor.getDirtyCount(), result)

number of changes is 0, even though the result is the same - the page is loaded. Since in my project I desperately need to be able to load the page at a specific time this is messing everything up. I also tried clearing the number of changes after loading, but since the code that sets it does so in a setTimeout() callback it's not possible to do it deterministically.

I beg your pardon? Are you quite serious that it is the "expected" behavior? Have you seen that in any other editor out there that the project is automatically modified upon loading and then automatically saved? I find that hard to believe.

Thanks for reporting this, @padcom.

The issue with getDirtyCount() returns 1 after loading 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