Component with pointer-events: 'all' (except wrapper) or editable component are draggable & droppable to itself.
There was an issue with the demo itself which now it's fixed (added draggable: false to the wrapper component)
Read full answer below ↓Question
GrapesJS version
- I confirm to use the latest version of GrapesJS
What browser are you using?
Chrome 107.0.5304.121 (Official Build) (arm64)
Reproducible demo link
https://jsfiddle.net/artur_arseniev/aku70f5w
Describe the bug
How to reproduce the bug?
- Try to drag and drop the editable component or component having a
pointer-events: allCSS in itself. It will disappear. As this operation performs an infinite loop and returns an error on the consoleUncaught RangeError: Maximum call stack size exceeded. Even after setting draggable false to the editable component, it is draggable.
What is the expected behavior? The editable component should not be draggable to itself same as the wrapper component.
What is the current behavior? The editable component is draggable to itself. Even after setting it as draggable false.

Code of Conduct
- I agree to follow this project's Code of Conduct
Answers (3)
There was an issue with the demo itself which now it's fixed (added draggable: false to the wrapper component)
Patch for getCss to return always the content from the editable component is not working, can you please help me to solve this @artf The below code (present in the reproducible demo link) always returns the whole canvas or wrapper CSS string.
editor.getModel().getCss = () => {
const wrapper = editor.getWrapper();
const cmp = wrapper.findType('editable')[0];
return cmp ? editor.CodeManager.getCode(cmp, 'css') : '';
};
Thanks for reporting this, @FaisalShaikhHA.
Great question about Component with pointer-events: 'all' (except wrapper) or editable component are draggable & droppable to itself.. The recommended approach with StyleManager 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 #6659
Symbol styles not synced
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Firefox 145.0 (64-bit) Reproducible demo l...
Issue #5720
Propagating component defaults can break layers when child comments are introduced
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v122 Reproducible demo link https:/...
Issue #5424
`component:styleUpdate` event is not fired
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome 116.0.5845.187Reproducible demo link...
Issue #4897
component:styleUpdate / component:styleUpdate:propertyName not fired
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Edge 109.0.1518.70 Reproducible demo link...
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.