Issue #3392💬 AnsweredOpened April 7, 2021by rywilson280 reactions

Allow dynamic droppable configuration using a function

快速解答by rywilson28

Associated PR: https://github.com/artf/grapesjs/pull/3393

Read full answer below ↓

Question

I have a requirement where I cannot use selectors to determine if an element is droppable. For example:

image

The "child" component must be within a "parent" component, however if the child component contains a ref attribute it can only be dragged into other parent containers that match the same ref value as the current parent. Given the above markup, the child component can be dropped into the last container but not the container with the ref of 5678. However the second child element could be dropped into any of the parent components.

代码片段TEXT
This would easily be accomplished if droppable would allow a function:
        droppable: (src, target) => {
          //some logic
          return true;
        }, 

This would require a fairly simple change to the Sorter:

    // Check if the target could accept the source
    let droppable = trgModel.get('droppable');
    if (typeof droppable === 'function') {
      let res = droppable(src, trg);
      result.droppable = res;
      result.dropInfo = res;
      droppable = res;
    } else {
     //existing logic

Answers (3)

rywilson28April 21, 2021

@artf do have any questions regarding this feature or the approach taken in the PR?

ClaudeCodeMay 17, 2026

Thanks for reporting this, @rywilson28.

Great suggestion about FEAT: Allow dynamic droppable configuration using a function! 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.

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins →
Premium option

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.

All tutorials →

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.