Issue #5245πŸ’¬ AnsweredOpened July 16, 2023by riteshdalal0 reactions

Contents of component with editable:false are still editable

Quick answerby artf

The editable property has no meaning by default and it's only used internally by other extended components like Text or Image

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome 114.0.5735.198

Reproducible demo link

https://jsfiddle.net/riteshdalal/obnx7sg3/22/

Describe the bug

How to reproduce the bug?

  1. Create a component with editable:false in the model
  2. Drop the component on the canvas

What is the expected behavior? Contents of the non editable component should not be parsed by GJS

What is the current behavior? Contents of the non editable component are parsed and editable

Check the attached demo link

Code of Conduct

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

Answers (4)

artfβ€’ July 17, 2023

The editable property has no meaning by default and it's only used internally by other extended components like Text or Image

riteshdalalβ€’ July 17, 2023

@artf how do we create a component such that gjs does not parse the children.

riteshdalalβ€’ July 17, 2023

The editable property has no meaning by default and it's only used internally by other extended components like Text or Image

This used to work on older versions of GJS. Just stopped working in 0.21.3

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @riteshdalal.

Great question about Contents of component with editable:false are still editable. 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.