Component tools misalign when the editor is resized
Thanks @bernesto for the report but as we can't detect programmatic layout changes without impacting the performances, in this case, you have to update the editor layout manually via editor.refresh() (eg. in your example you would put the call right at the end of your resizeEditor function)
Read full answer below ↓Question
GrapesJS version
- I confirm to use the latest version of GrapesJS
What browser are you using?
Chrome v122
Reproducible demo link
https://jsfiddle.net/Lk2bwhp4/
Describe the bug
How to reproduce the bug?
- Place the editor inside of a container, then programmatically resize the container's width.
What is the expected behavior? The editor and all of its children should resize accordingly.
What is the current behavior? All component's canvas spots in the editor retain their offsets from prior to the canvas resize.
- Note, a window resize of resets the positions. This must be done programmatically in the window. Use cases would be where the editor is on a page with other panels that may resize the available space for the editor.
- In the example below, view how the tools align to the related element after resizing the editor to a larger width. The tools are left at the old location until an event triggers an update. A window resize or preview toggle will update the view.
Code of Conduct
- I agree to follow this project's Code of Conduct
Answers (4)
Thanks @bernesto for the report but as we can't detect programmatic layout changes without impacting the performances, in this case, you have to update the editor layout manually via editor.refresh() (eg. in your example you would put the call right at the end of your resizeEditor function)
Hi @artf, I actually had this accidentally mixed in the last pull request you accepted (src/canvas/model/Frame.ts). You might want to take a look at what I added and see if it is causing an issue. We have it in testing right now and haven't seen a degradation in performance and it addresses the issue.
I actually had this accidentally mixed in the last pull request you accepted
and I actually removed it cause it seemed to be unrelated 🤣
Not a problem to add it back but consider that your example will work only because of the desktop Device. The width is filling the container and that triggers the iframe window resize (which then will trigger the added event). It won't work in case you change to a smaller Device, in that case no resize event will be triggered so you still need the refresh call.
Thanks for reporting this, @bernesto.
Great question about Component tools misalign when the editor is resized. The recommended approach with Canvas is to use the event-driven API.
Start here:
- Check the GrapesJS documentation for your specific module
- Look for the
on()event listener method - 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.
Issue #6269
Component model and view inits every time it's dragged over every component present in Canvas on which it can be dropped into
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Version 130.0.6723.59 (Official Bui...
Issue #5280
Event handler on view not bound to the component
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Version 115.0.5790.114 Reproducible...
Issue #6458
sector.setName doesn't work
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link https://jsfi...
Issue #5316
Editor not subscribing to selector:remove
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v115.0.5790.170 Reproducible demo lin...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins →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.
Tutorial
Find the Right GrapesJS Plugin in Seconds: Smarter Discovery Is Live
We're shipping a set of discovery upgrades. New label filters, a proper compatibility switch for GrapesJS vs Studio, one-click and a smarter sort bar.
Tutorial
GrapesJS vs Webflow vs Tilda: What to Choose for Your Business in 2026
Choosing the right website platform in 2026 is no longer just about building a site
Tutorial
GJS Market 2.0 - Donations, Tracking, Labels and Better Product Discovery
We’ve rolled out a new set of GrapesJS marketplace updates across GJS Market, focused on improving how creators distribute products
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.