BUG (v0.16.41): Button component with draggable property is not working properly

I guess you're doing something wrong, how do you create those components and their properties?? You shouldn't even see those attributes in the inspector.

@artf In our codes we have not changed anything. The only difference is that we update the GrapesJs version. Before I had version v0.16.18 and it worked correctly, but now we update GrapesJs to v0.16.41 and it doesn't work for buttons.

we set the properties with this:

editor.getSelected().attributes.attributes["data-gjs-editable"] = 'false'
editor.getSelected().attributes.attributes["data-gjs-copyable"] = 'false'
editor.getSelected().attributes.attributes["data-gjs-droppable"] = 'false'
editor.getSelected().attributes.attributes["data-gjs-draggable"] = 'false'
editor.getSelected().attributes.attributes["data-gjs-resizable"] = 'false'
editor.getSelected().attributes.attributes["data-gjs-stylable"] = 'false'

this way was working perfectly for v0.16.18

Thanks for reporting this, @marcepoblet.

The issue with BUG (v0.16.41): Button component with draggable property is not working properly 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:

1. Add a setTimeout wrapper to ensure the DOM has settled:

setTimeout(() => {
  // your operation here
}, 0);

2. Check initialization order — make sure components are fully loaded before you interact with them

3. 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