BUG: `getDirtyCount()` returns `1` after loading
Question
GrapesJS version
- I confirm to use the latest version of GrapesJS
What browser are you using?
Chrome latest
Reproducible demo link
https://github.com/padcom/grapes-bug-dirty-after-loading/blob/master/src/App.vue#L37
Describe the bug
- Clone and start the project
git clone https://github.com/padcom/grapes-bug-dirty-after-loading
cd grapes-bug-dirty-after-loading
npm i
npm start
- Open console
Current behavior: number of changes is 1 Expected behavior: number of changes is 0
Additional note: when using autoload number of changes stays at 0
Code of Conduct
- I agree to follow this project's Code of Conduct
Answers (3)
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.
Related Questions and Answers
Continue research with similar issue discussions.
Issue #5385
BUG: getDirtyCount() non deterministic after load
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link https://gith...
Issue #5274
BUG: Parser bug inside Remix
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v114 Reproducible demo link https:/...
Issue #5263
BUG: Deleting a component without deleting its corresponding style, will adding new components later cause style conflicts?
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? latest version of Chrome Reproducible demo...
Issue #5613
BUG: Incorrect type definition for StyleManagerConfig.sectors.properties
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link None Describ...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.