Issue #5385Opened September 14, 2023by padcom0 reactions

BUG: getDirtyCount() non deterministic after load

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome

Reproducible demo link

https://github.com/padcom/grapesjs-bug-dirty-count-non-deterministic/blob/master/index.html

Describe the bug

Currently, when the user calls await load() the dirty count is zero. Only after the next event loop or later the count is increased. Therefore:

await editor.load()
console.log(editor.getDirtyCount())

prints out 0 but after a milisecond:

setTimeout(() => console.log(editor.getDirtyCount(), 1)

the number of changes is 1.

Expected behavior is that after awaiting the call to load(), if indeed as described in #5373 the editor is changed it should be so immediately after the call to load()


### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

Answers (3)

artfSeptember 16, 20230 reactions

Added also load options in order to clear the editor internal state post load

const storageOptions = {};
const loadOptions = { clear: true };
await editor.load(storageOptions, loadOptions);
editor.getDirtyCount(); // should always be 0 post load
padcomSeptember 18, 20230 reactions

Thank you! Looking forward to the next release!

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

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.