Issue #5630πŸ’¬ AnsweredOpened January 18, 2024by kla-ko0 reactions

Configuring an onStart() resize callback prevents resizing

Quick answerby artf

Good catch, will fix it

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome Version 120.0.6099.225

Reproducible demo link

https://jsfiddle.net/wattnu/y8L6whun/

Describe the bug

How to reproduce the bug?

  1. Goto jsfiddle
  2. run the code
  3. on the canvas, select the blue div component
  4. try to drag the resizer handle located at bottom center
  5. the resize handle doesn't move with your mouse
  6. In the js code, check my plugin implementation on the top. There, consider the part:
 resizable: {
          tl: 0, tc: 0, tr: 0, cl: 0, cr: 0, bl: 0, bc: 1, br: 0, 
          onStart: (event, opt) => { console.log('resize started') } ,
        },
  1. comment out the onStart config --> // onStart: (event, opt) => { console.log('resize started') } ,
  2. re-run the fiddle. Now it is possible to resize the blue block.

What is the expected behavior? The component should be resizable even when configuring an onStart calback

What is the current behavior? The component cannot be resized if an onStart callback is configured. The callback is executed though.

Code of Conduct

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

Answers (2)

artfβ€’ January 18, 2024

Good catch, will fix it

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @kla-ko.

Great question about configuring an onStart() resize callback prevents resizing. The recommended approach with ProseMirror 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.