Issue #4546✓ SolvedOpened September 2, 2022by FaisalShaikhHA2 reactions

Component disappears when we select all the inner text and use backspace. Link component disappears even when we try to update the text.

Quick answerby artf2

This happening due to these styles. Remove them and it will work properly.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Version 104.0.5112.101 (Official Build) (arm64)

Reproducible demo link

https://codepen.io/faisal-praella/pen/rNvOwgR

Describe the bug

How to reproduce the bug?

  1. Select a component, double click, and ctrl+a to select the text and click backspace.
  2. Notice component disappears, and is not selectable or editable.

What is the expected behavior? The component should not disappear.

What is the current behavior? Component disappears, and is not selectable or editable.

https://user-images.githubusercontent.com/102785785/188111128-9b174ea7-590b-4552-86d2-a93d214a2588.mp4

Code of Conduct

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

Answers (4)

👍 Most helpfulartfSeptember 8, 2022

This happening due to these styles. Schermata 2022-09-08 alle 15 09 38 Remove them and it will work properly.

artfSeptember 6, 2022

@FaisalShaikhHA are you able to provide a reproducible demo as I'm not able to reproduce it from the official demo?

FaisalShaikhHASeptember 7, 2022

@artf here is the demo: https://codepen.io/faisal-praella/pen/rNvOwgR Select a component, double click, and ctrl+a to select the text and click backspace. Notice component disappears, and is not selectable or editable. Link component disappears even when we try to update the text. Please refer above video.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @FaisalShaikhHA.

Great question about Component disappears when we select all the inner text and use backspace. Link component disappears even when we try to update the text.. The recommended approach with Components 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.