Issue #3352Opened March 19, 2021by harsh2011 reactions

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

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 (3)

artfMarch 22, 20211 reactions

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.

harsh201March 22, 20210 reactions

@artf Any help here?

harsh201March 22, 20210 reactions

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

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

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.