Improve and fix absolute dragMode

Hi everyone,

Thanks a lot for the feedback and detailed discussion.

We’re happy to share that we’ve addressed some of the requested functionality. Also, we’ve introduced a new absolute mode plugin that should cover most of the use cases mentioned above.

You can read more about it in our new documentation here:

• https://app.grapesjs.com/docs-sdk/plugins/canvas/absolute-mode

Feel free to try it out and let us know if you have any further suggestions!

Hi @artf, this feature is crucial for my current project, so I have two questions:

1. Is it possible to pay you (or someone else) to prioritize this feature?
2. If not, can you outline the steps necessary to resolve the issue and give me a starting point?

Thanks for reporting this, @damnslow.

Great suggestion about [Feature]: Improve and fix absolute dragMode! While this specific feature isn't yet in the core API, there are several ways to achieve similar behavior.

Using the event system:

editor.on('component:update', (component) => {
  // your logic here
});

Alternative approaches:

• Listen to selector:add for CSS selector changes
• Use selector:custom for custom rules
• Tap into the change:* events for fine-grained tracking
• Build a plugin that extends the editor with this capability

Making it official: If this feature would benefit many users, consider opening a formal Feature Request on the GrapesJS repo with:

• A detailed use case
• Code example showing the desired behavior
• Why this matters for your workflow

The core team is receptive to well-motivated feature requests backed by real use cases.