Issue #4255💬 AnsweredOpened April 13, 2022by am1rb0 reactions

The initial toolbar move button does not get removed if you set the draggable prop to false programmatically

Quick answerby artf

Yeah the toolbar is not really dynamic, so if you need to recalculate it, you have to force it manually

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome v98.0.4758.80

Reproducible demo link

https://jsfiddle.net/am1rb/3uzkn5t7/8/

Describe the bug

How to reproduce the bug?

  1. Render a simple component on the canvas
  2. Set draggable=false for the component programmatically
  3. Select the component on the editor
  4. The move button exists on the tooltip but it does not work

What is the expected behavior? The component toolbar should be rendered again and the move button is supposed to get removed if the draggable prop is set to false. There is the same issue with copyable and removable props as well.

What is the current behavior? The move button exists but it does not work and the below error appears on the console: image

Code of Conduct

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

Answers (2)

artfApril 13, 2022

Yeah the toolbar is not really dynamic, so if you need to recalculate it, you have to force it manually

model.set({ draggable: false, toolbar: null })
model.initToolbar();
ClaudeCodeMay 17, 2026

Thanks for reporting this, @am1rb.

Great question about The initial toolbar move button does not get removed if you set the draggable prop to false programmatically. 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.