Issue #3434💬 AnsweredOpened May 5, 2021by advancedsoftwarecanada1 reactions

Using imported HTML/CSS/JS into the editor shows outlines, but no content, JS Fiddle inside

Quick answerby advancedsoftwarecanada1

This issue can be resolved. I simply switched out the HTML/JS application to flat HTML -- disabled all the stupid loading effects. I'll just have an external script when not in editor do fancy stuff. ALL HAIL GRAPEJS.

Read full answer below ↓

Question

You can get the version by typing grapesjs.version into the console YES: https://jsfiddle.net/75a9u1cf/2/

What is the expected behavior? I am expecting to be able to edit the HTML and content in the editor

Describe the bug detailed The screen is simply white, I can see the shapes and drag elements, but the editor is just not displaying the content

HALF-SOLVED: https://jsfiddle.net/75a9u1cf/3/

Answers (4)

advancedsoftwarecanadaMay 7, 2021

This issue can be resolved. I simply switched out the HTML/JS application to flat HTML -- disabled all the stupid loading effects. I'll just have an external script when not in editor do fancy stuff.

ALL HAIL GRAPEJS.

advancedsoftwarecanadaMay 5, 2021

image

advancedsoftwarecanadaMay 5, 2021

HALF SOLVED IT, found some stuff on Google:

https://jsfiddle.net/75a9u1cf/3/

But some images still don't work.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @advancedsoftwarecanada.

The issue with Using imported HTML/CSS/JS into the editor shows outlines, but no content, JS Fiddle inside 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 →

Related tutorials

In-depth guides on the same topic.

All tutorials →

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.