Option resizable:true will change all the same components in canvas.
Question
WARNING
READ and FOLLOW next 3 steps, then REMOVE them before posting the issue
- Follow CONTRIBUTING Guidelines https://github.com/artf/grapesjs/blob/master/CONTRIBUTING.md
- Do a quick SEARCH first, to see if someone else didn't open the same issue
- All relative statements/questions have to be filled/answered, otherwise, the issue might be CLOSED
- JSFiddle Starter template https://jsfiddle.net/szLp8h4n
- CodeSandbox Starter template https://codesandbox.io/s/1r0w2pk1vl
Version: grapesjs-0.17.22
Are you able to reproduce the bug from the demo?
- [*] Yes
- No
What is the expected behavior? When changing the size of an element, it should not cause other same components to change at the same time.
Describe the bug detailed
I saw that the resizable of image video is correct. This is the case with my customization. The reason for this is that the style name is used when the change is made.
What is the current behavior?
Describe the bug detailed
Are you able to attach screenshots, screencasts or a live demo?
editor.DomComponents.addType('section', {
isComponent: el => el.className === 'bui-section',
// Model definition
model: {
// Default properties
defaults: {
tagName: 'div',
name: "section",
droppable: false, // Can't drop other elements inside
resizable: true,
attributes: { // Default attributes
className: 'bui-section',
},
traits: [
'name',
],
components: `Text`,
}
}
});
editor.addComponents(`<div class="bui-section">BUI</div>`)
- [*] Yes (attach)
- No

Answers (2)
Use component first styling
grapesjs.init({
...
selectorManager: {
componentFirst: true,
...
},
})
Thanks for reporting this, @imouou.
The issue with option resizable:true will change all the same components in canvas. 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:
- Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
// your operation here
}, 0);
-
Check initialization order — make sure components are fully loaded before you interact with them
-
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.
Issue #3703
custom ids have a \3 injected into the css and a space after the following letter after the \3 when added to the canvas
WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grape...
Issue #3463
inspector overflow broken
WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grape...
Issue #3511
Command core:component-enter not working in all the cases
WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grape...
Issue #3700
setting draggable: 'wrapper' does not drop in wrapper
WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grape...
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.