Issue #3634💬 AnsweredOpened July 22, 2021by pankajsharma891 reactions

How we can hide RTE for editable components ?

快速解答by mcottret1

I allow myself to add what I think might be closer to what OP's trying to achieve, from @artf's answer: Toggling the disableRte property allows to hide the RTE toolbar, while keeping the text editable, on a per-component basis. Hope this helps :)

Read full answer below ↓

Question

HI We have a requirement, where we don't want to show rte on editable components. how we can achieve that ?

Answers (4)

mcottretOctober 29, 2021

I allow myself to add what I think might be closer to what OP's trying to achieve, from @artf's answer:

editor.DomComponents.addType('text', {
    extendFnView: ['onActive'],
    model: {
      defaults: {       
        disableRte: false
      }
    },
    view: {
      onActive() {
        if (this.model.get('disableRte')) {
          this.rte.getToolbarEl().style.display = 'none';
        }
      }
    }
}

Toggling the disableRte property allows to hide the RTE toolbar, while keeping the text editable, on a per-component basis.

Hope this helps :)

iabhiyaanJuly 25, 2021
editor.on('component:selected', cmp => {
  cmp.set({
   editable: false,
   propagate: ['editable']
 })
})
pankajsharma89July 25, 2021

We don't want to make component non editable, component needs to be editable, we just don't want to show rte tool bar on that component.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @pankajsharma89.

Great question about [Question] - How we can hide RTE for editable components ?. 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.