Issue #6373πŸ’¬ AnsweredOpened January 16, 2025by ChipiKaf1 reactions

Resizing of Child with absolute drag enabled positions element wrongly when in Parent with relative position

Quick answerby ChipiKaf❀ 1

@artf I have a fix for it locally. Essentially what I do is check if the element has a parent with relative position, then offset the rect by the height of the parent if it exists and is position relative. I can create a PR for it if that's fine?

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Version 131.0.6778.265

Reproducible demo link

https://codepen.io/chipikaf/pen/KwPexjL

Describe the bug

How to reproduce the bug?

  1. Drop the button component in the Middle section
  2. Move the button anywhere in the section
  3. Resize element

What is the expected behavior? For the element to be resized in its original position

What is the current behavior? The element is moved below to an unexpected position

Code of Conduct

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

Answers (2)

ChipiKafβ€’ January 16, 2025

@artf I have a fix for it locally. Essentially what I do is check if the element has a parent with relative position, then offset the rect by the height of the parent if it exists and is position relative.

I can create a PR for it if that's fine?

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @ChipiKaf.

Great question about Resizing of Child with absolute drag enabled positions element wrongly when in Parent with relative position. The recommended approach with Components 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.