Issue #4506💬 AnsweredOpened August 10, 2022by tyuterry0 reactions

Error on drag block with dragmode: absolute

Quick answerby artf

Thanks @tyutony the issue was fixed already (https://github.com/artf/grapesjs/pull/4487). Unfortunately, the only workaround now would be to expose globally the editor instance (window.editor = grapesjs.init({...}))

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome v103

Reproducible demo link

https://stackblitz.com/edit/js-1xpo7b

Describe the bug

How to reproduce the bug?

  1. use dragMode: absolute (designer mode)
  2. drag a block from Block Manager

Can not reproduce on JSFiddle here but i dont know how.

I guess is CDNs grapesjs is different with npm version grapesjs.

What is the expected behavior? No error and editor not stuck

What is the current behavior? Console Error : editor is not defined and editor stuck

1660117887338

Code of Conduct

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

Answers (4)

artfAugust 12, 2022

Thanks @tyutony the issue was fixed already (https://github.com/artf/grapesjs/pull/4487). Unfortunately, the only workaround now would be to expose globally the editor instance (window.editor = grapesjs.init({...}))

wunksertSeptember 15, 2022

@tyutony I'm experiencing this same thing, did you find a workaround? Doesn't seem like the bug is fixed

artfSeptember 15, 2022

@wunksert it's fixed but not yet released (the new release will be published soon)

ClaudeCodeMay 17, 2026

Thanks for reporting this, @tyuterry.

Great question about Error on drag block with dragmode: absolute. The recommended approach with GrapesJS 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.