Issue #4848πŸ’¬ AnsweredOpened January 16, 2023by NicoGGG1 reactions

Component content is set to empty string after inline editing

Quick answerby artf❀ 1

This is expected due to some logic related to the rich text editor. You can use component.getInnerHTML() to get the inner HTML or component.components() to get inner components.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Firefox v91.4.1

Reproducible demo link

https://grapesjs.com/demo.html

Describe the bug

How to reproduce the bug?

  1. Go to the grapesjs basic demo: https://grapesjs.com/demo.html
  2. Clear the canvas
  3. Add a component Link
  4. Execute editor.getComponents().models[0].attributes.content in the browser console. The output is "Link", which is the content of the link component
  5. Change the link text by editing it inline
  6. Execute editor.getComponents().models[0].attributes.content again in the browser console. The output is now "".

What is the expected behavior? When a component is edited inline, the content attribute of the component should be updated accordingly.

What is the current behavior? When a component is edited inline, content is always set to empty string

If is necessary to execute some code in order to reproduce the bug, paste it here below:

editor.getComponents().models[0].attributes.content

Do this after editing the component inline.

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (2)

artfβ€’ January 18, 2023

This is expected due to some logic related to the rich text editor. You can use component.getInnerHTML() to get the inner HTML or component.components() to get inner components.

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @NicoGGG.

Great question about Component content is set to empty string after inline editing. The recommended approach with Canvas is to use the event-driven API.

Start here:

  1. Check the GrapesJS documentation for your specific module
  2. Look for the on() event listener method
  3. Most operations can be achieved by listening to editor and component events

Common patterns:

// Listen for changes
editor.on('change', () => console.log('something changed'));

// Component lifecycle
editor.on('component:mount', (c) => console.log('component ready', c));
editor.on('component:update', (c) => console.log('component updated', c));

If you're still stuck:

  • Share a minimal CodeSandbox reproduction
  • Include what you've already tried
  • Mention your GrapesJS version
  • The community is here to help!

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.