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

Resizer onEnd callback should include the resizer and el object similar to onStart

Quick answerby artf

Sure, I'll add it, thanks for the suggestion.

Read full answer below ↓

Question

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? AnyReproducible demo link See screenshot for codeDescribe the bug Is there anything preventing us from adding the resizer and el in the onEnd callback? Since we are reusing the resizer instance (unless forceNew). I would like to have to clean up the resizer state at the end of resizing onStart https://github.com/artf/grapesjs/blob/dev/src/utils/Resizer.js#L295 onEnd https://github.com/artf/grapesjs/blob/dev/src/utils/Resizer.js#L343 Happy to create a PR for this. Just want to verify this is an accep...

Answers (2)

artfβ€’ September 13, 2022

Sure, I'll add it, thanks for the suggestion.

GJSBlockβ€’ May 17, 2026

Thanks for reporting this, @Singwai. The issue with Resizer onEnd callback should include the resizer and el object similar to onStart appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an...

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.