Issue #4580πŸ’¬ AnsweredOpened September 13, 2022by Singwai0 reactions

Resizer cursor's starting position should also use the `mousePosFetcher` if provided.

Quick answerby artf

Yeah, you're right, I'll fix it, thanks for the report.

Read full answer below ↓

Question

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? anyReproducible demo link anyDescribe the bug Start Pos should also use the MosePosFetcher method if the override is provided right?Start Pos https://github.com/artf/grapesjs/blob/dev/src/utils/Resizer.js#L278-L281Current Pos https://github.com/artf/grapesjs/blob/dev/src/utils/Resizer.js#L306-L312 Happy to create a PR for this, just want to make sure that is a desired behavior.Code of Conduct[X] I agree to follow this project's Code of Conduct

Answers (2)

artfβ€’ September 13, 2022

Yeah, you're right, I'll fix it, thanks for the report.

GJSBlockβ€’ May 17, 2026

Thanks for reporting this, @Singwai. The issue with Resizer cursor's starting position should also use the mousePosFetcher if provided. appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating a...

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.