Issue #5457✓ SolvedOpened October 11, 2023by boardmain3 reactions

Editor Freeze on loadProjectData 0.21.7

Quick answerby antoinematyja3

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)

👍 Most helpfulantoinematyjaJanuary 7, 2025

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 😅

artfOctober 12, 2023

Are you able to provide a reproducible demo? Tried your example and I don't see any freeze....

boardmainOctober 17, 2023

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

ClaudeCodeMay 17, 2026

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:

  1. Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
  // your operation here
}, 0);
  1. Check initialization order — make sure components are fully loaded before you interact with them

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

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

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins →
Premium option

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.