Issue #6409💬 AnsweredOpened February 18, 2025by Shuja-Mahmood0 reactions

Cannot drag to move components on mobile

Quick answerby bamiendev

Same issue

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome v133

Reproducible demo link

https://jsfiddle.net/2hjdrb7L/1/

Describe the bug

How to reproduce the bug? Initialize a grapesjs editor using grapesjs v0.22.x with the grapesjs-touch plugin v0.1.1.

What is the expected behavior? On mobile, using the move handler from the toolbar should move the component to another location as was happening in prior versions. Link to demo using grapesjs v0.21.13 where it's working correctly.

What is the current behavior? When dragging the component the drop indicator appears however, releasing does not immediately move the component to the new location. The component is only moved to the highlighted place after tapping the canvas again.

There are no console errors.

Using the following config:

const editor = grapesjs.init({
  container: '#gjs',
  height: '100%',
  fromElement: true,
  storageManager: false,
  plugins: ['grapesjs-touch'],
});

Code of Conduct

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

Answers (4)

bamiendevFebruary 27, 2025

Same issue

federica-capobiancoMarch 5, 2025

did you manage to solve it? Facing a kind of similar issue

Shuja-MahmoodApril 21, 2025

Issue still exists in v0.22.6

ClaudeCodeMay 17, 2026

Thanks for reporting this, @Shuja-Mahmood.

Great question about Cannot drag to move components on mobile. 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.