Issue #5888💬 AnsweredOpened May 16, 2024by Dobby851 reactions

Cannot edit component content even with editable property set to true

Quick answerby Dobby851

By looking into the code, I saw that to get the RTE functionnality, our new component has to extend ComponentTextView. My initial issue was that I did something like : And it tooks the view of my baseStructure and not the text component. I will try to find a workaround for that by don't extending my baseStructure view.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome V124

Reproducible demo link

https://jsfiddle.net/ycvz2gno/7/

Describe the bug

How to reproduce the bug?

  1. Put a text block in the canvas
  2. Double click on the content inside the text block
  3. The content cannot be edited

What is the expected behavior? It should open the RTE so we could edit the text inside the component

What is the current behavior? Nothing happened, the component cannot be edited



### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

Answers (2)

Dobby85May 16, 2024

By looking into the code, I saw that to get the RTE functionnality, our new component has to extend ComponentTextView. My initial issue was that I did something like :

editor.DomComponents.addType('textBlock', {
    isComponent: el => el.tagName === 'DIV',
    extend: 'text',
    model: {
      defaults: {
        editable: true,
        tagName: 'div',
        icon: 'ICON',
        components: `Some text`
      }
    },
    extendView: 'baseStructure'
  })

And it tooks the view of my baseStructure and not the text component. I will try to find a workaround for that by don't extending my baseStructure view.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @Dobby85.

Great question about Cannot edit component content even with editable property set to true. The recommended approach with ProseMirror 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.