Issue #3352πŸ’¬ AnsweredOpened March 19, 2021by harsh2011 reactions

Default Content is getting Inserted while using setComponents if Tag Body is empty

Quick answerby artf❀ 1

You have defined the default content in the component definition, so, an empty one will use that as default. Just move that content from component definition to the paragraph block.

Read full answer below ↓

Question

Version: Latest

You can get the version by typing grapesjs.version into the console

Are you able to reproduce the bug from the demo?

  • Yes
  • No

What is the expected behavior? Component with empty body should not be populated with default content.

What is the current behavior? When we create an empty node and pass it on to GrapesJS as input using setComponents(), the component extending TextNode adds default content if tag body is empty.

Describe the bug detailed When we create an empty node and pass it on to GrapesJS as input using setComponents(), the component extending TextNode adds default content if tag body is empty. We have use cases where some tags might be empty. Is there a way we can handle where we can disable it inserting it via setComponents?

Demo: https://jsfiddle.net/senbyh2g/1/

Answers (4)

artfβ€’ March 22, 2021

You have defined the default content in the component definition, so, an empty one will use that as default. Just move that content from component definition to the paragraph block.

harsh201β€’ March 22, 2021

@artf Any help here?

harsh201β€’ March 22, 2021

Thanks @artf! Completely forgot about adding at block level.

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @harsh201.

The issue with Default Content is getting Inserted while using setComponents if Tag Body is empty 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.