Issue #6654💬 AnsweredOpened November 19, 2025by zjt-dev0 reactions

The rich-text editor cannot be activated

Quick answerby artf

By default the text component is activated with a double-click https://github.com/GrapesJS/grapesjs/blob/f59e981f76ff378f59c06cf706af88e502db098e/packages/core/src/dom_components/view/ComponentTextView.ts#L22

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

chrome v91

Reproducible demo link

https://codepen.io/asenper/pen/QwNMwpV

Describe the bug

I expect the RTE to open when clicking on the text, but nothing happens.

Is this a bug or am I missing additional configuration?

Code of Conduct

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

Answers (4)

zjt-devNovember 21, 2025
<img width="1382" height="393" alt="Image" src="https://github.com/user-attachments/assets/6a3850b9-91ed-43de-b9ae-1a2f703e6f02" /> <img width="695" height="468" alt="Image" src="https://github.com/user-attachments/assets/2a62ad3b-ed7a-4d8c-8c12-21898bed3fb8" />

How should I solve or avoid this problem

artfNovember 21, 2025

When you import generic HTML it's hard to detect text components properly. If you have the ability to edit HTML you can enforce it via gjs attributes <div data-gjs-type="text">Insert....

ClaudeCodeMay 17, 2026

Thanks for reporting this, @zjt-dev.

The issue with the rich-text editor cannot be activated 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.