Issue #5339💬 AnsweredOpened August 26, 2023by rozek0 reactions

question style-manager components bug typescript

DragMode:'absolute' behaves strange

Quick answerby rozek

sorry - this was a problem on my side which became obvious within the editor only - sorry for bothering!

Read full answer below ↓

Question

GrapesJS version

I confirm to use the latest version of GrapesJS

What browser are you using?

Version 1.56.20 Chromium: 115.0.5790.171 (Offizieller Build) (arm64)

Reproducible demo link

none

Describe the bug

I want the components in my editor to be moveable by dragging. After some research, I found that

let Editor = grapesjs.init({
  dragMode:'absolute',

is needed to achieve this functionality. At least, my components can now be moved...but, since the editor uses a wrapper around the actual component view, the wrapper position may be correct, but the view position is now measured relative to the wrapper, which is wrong:

The technical reason for this behaviour (and why I consider this as a "bug") is that both the wrapper and its content get the same HTML id assigned to them - which is always wrong as such ids must be unique within an HTML document:

The elements in the DOM:

...and their CSS settings:

As a consequence, the same styling is applied to both

Code of Conduct

I agree to follow this project's Code of Conduct

Answers (2)

rozek• August 26, 2023

sorry - this was a problem on my side which became obvious within the editor only - sorry for bothering!

ClaudeCode• May 17, 2026

Thanks for reporting this, @rozek.

The issue with dragMode:'absolute' behaves strange appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state.

What to try:

Add a setTimeout wrapper to ensure the DOM has settled:

setTimeout(() => {
  // your operation here
}, 0);

Check initialization order — make sure components are fully loaded before you interact with them
Use the editor's event system — listen to completion events:

editor.on('component:mount', (component) => {
  // safe to interact with component here
});

Recommended next steps:

Test with the latest GrapesJS version if you haven't
Provide a minimal reproducible example (CodeSandbox) — this helps the team identify the root cause faster
Include GrapesJS version, browser, and console errors in your report

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 →

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.

Presets Plugins Components Blocks Assets Commands I18n Layers Styles Storages RTE Newsletters Web pages Site builders

DragMode:'absolute' behaves strange

Question

GrapesJS version

What browser are you using?

Reproducible demo link

Describe the bug

Code of Conduct

Answers (2)

Related Questions and Answers

draggable/droppable property functions not called while dragging

Uncaught SyntaxError: Unexpected token '{' at CanvasView.ts:590:12

Component script function runs twice after page save

update() of custom types added to StyleManager is no more triggered when switching between some targets.

Paid Plugins That Match This Issue

Related tutorials

How to Build a Production GrapesJS Editor: The Complete Walkthrough of Brief, Preset, Plugins, and Services

Big Updates: TinyMCE 8 and Placeholder 2.0 for GrapesJS

Find the Right GrapesJS Plugin in Seconds: Smarter Discovery Is Live

Browse Plugin Categories