Editor Freeze on loadProjectData 0.21.7
Hi, I encountered the same issue using Vue 3 and using a vue ref to store the editor. Not sure if this is a good idea though. A code reproduction would be something like: Fix: don't use a ref 😅
Read full answer below ↓Question
GrapesJS version
- I confirm to use the latest version of GrapesJS
What browser are you using?
Chrome 117.0
Reproducible demo link
localhost
Describe the bug
grapesjs": "^0.21.7",
editor.loadProjectData({ "assets": [], "styles": [], "pages": [{ "component": "<div>TEST TEST TEST TEST</div>" }] })
editor freeze
Code of Conduct
- I agree to follow this project's Code of Conduct
Answers (4)
Hi, I encountered the same issue using Vue 3 and using a vue ref to store the editor. Not sure if this is a good idea though.
A code reproduction would be something like:
<script setup>
// import vue ref
import { ref } from 'vue'
const editor = ref(null)
editor.value = grapesjs.init({
container: '#gjs',
...
})
// This makes the browser view freeze
editor.loadProjectData({ ... })
</script>
<template>
<div id="gjs" />
</template>
Fix: don't use a ref 😅
Are you able to provide a reproducible demo? Tried your example and I don't see any freeze....
tried with the latest version 21.7 i try to put it online, but i just pasted html from a custom command, the source is pasted, but after it, the editor freeze ( i need to close the page )
for example
btnImp.onclick = () => {
editor.runCommand('core:canvas-clear')
// editor.Css.clear()
editor.setComponents(codeViewer.getContent().trim())
editor.Modal.close()
}
where the codeViewer.getContent().trim() get simple html from a modal
Thanks for reporting this, @boardmain.
The issue with Editor Freeze on loadProjectData 0.21.7 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:
- Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
// your operation here
}, 0);
-
Check initialization order — make sure components are fully loaded before you interact with them
-
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
Related Questions and Answers
Continue research with similar issue discussions.
Issue #5263
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 #5105
Adding style o component by (prop, value), isn't work correct.
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome@latest Reproducible demo link https...
Issue #5019
Can't set preview mode on editor init when using loadProjectData()
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v111 Reproducible demo link https:/...
Issue #4792
Drag and drop broken in 20.2
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v108Reproducible demo link see belowD...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins →Premium plugins ship with support, regular updates, and production-ready features — save days of integration work.
Browse premium plugins →Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.