Issue #3699πŸ’¬ AnsweredOpened August 12, 2021by diegoSenra0 reactions

Cell hovering randomly displaces from actual cell

Quick answerby artf

Are you using the latest version?

Read full answer below ↓

Question

Hi!

I'm using grapesJs for e-mail editing in a project in my company, with Newsletter plugin. Everithing works very well, except for this bug i can't solve:

Sometimes, when I drag blocks inside the canvas, the cell hover gets scrambled. The biggest problem is that this behavior is completely random, it can happen or not but it's quite annoying when it does.

The only patterns are:

  • Scrambles ONLY AND EXCLUSIVELY right after dropping a block in canvas
  • If i resize the canvas for mobile/tablet it gets back to normal (even if turning back to desktop view - but it may happen again upon dropping new blocks)
  • The displacement only occurs vertically (randomly up or down - usually up - and can be any displacement size)
  • The cell options menu (select parent, move component, erase cell etc) is displaced too, in the same way.

The editor is inserted in a page with some more content (sidebar and header). I had to change the css of some editor classes to fit and look well in this page, unfortunatelly i dont remember exactly what attr i did change (although i dont think this would be the problem as it works well initially and it gets corrected if changing to mobile view).

The problem could be on my side, but I would like to know at least where could i look towards to better investigate this bug. Any help would be appreciated!

Below, pic of hover and options menu displaced

grapesJsBug

Answers (4)

artfβ€’ August 13, 2021

Are you using the latest version?

diegoSenraβ€’ August 16, 2021

Using minified 0.10.7

artfβ€’ August 16, 2021

Sorry mate, it's a 4-year-old release, can't help you here. Did you try to update?

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @diegoSenra.

The issue with Cell hovering randomly displaces from actual cell 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:

  1. Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
  // your operation here
}, 0);
  1. Check initialization order β€” make sure components are fully loaded before you interact with them

  2. 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

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.