Mouse & Element Positions + Draggable Plugin for Bubble

Need help Plugins
1

Hi there. :wave:

This thread will be dedicated to our Mouse & Element Positions + Draggable plugin discussions and user reports. :rocket:

And meanwhile, we would like to introduce the redesigned plugin demo page. Check it out here:
image

We hope it will be more convenient for everyone to see the plugin’s functionalities and ways of its implementation.

:sunflower:

Best,
Zeroqode Support Team

3 Likes
2

Hi everyone,

We’re excited to announce a major update for the Mouse & Element Positions + Move Plugin! The latest version introduces a fantastic new feature: Dynamic Element to X,Y EndUserControls.

image
image871×504 17.1 KB

With this new action, you can now dynamically move elements on the page or inside a Repeating Group—by using dynamically the current cell ID. This unlocks endless use cases, such as:

  • Moving elements based on the data in the current cell.
  • Building more interactive and dynamic UI elements for your app.
  • Creating complex behaviors like animated element movements tied to user input.

It’s incredibly flexible and powerful, so we encourage you to give it a try and see how it can enhance your app. You can now set element IDs dynamically, which will open up even more possibilities for interaction and responsiveness in your projects.

Here’s a simple test page, where you can try out the new action in action:
:backhand_index_pointing_right: Demo Page

For more workflow examples please check the plugin demo page here: https://zeroqode-demo-10.bubbleapps.io/mouse-position
And make sure to review the supporting documentation if you need to find more info about the plugin.

Feel free to play around with the new feature and let us know if you have any questions, feedback, or need further recommendations. We’re here to help and would love to hear your thoughts on this update!

Thanks,
Zeroqode Support Team

1 Like
3

Hi, how is it possible to disable an element’s drag? before there was the option to input key (disabled) and value (element id), but that is gone and now I only have the ID field. Using this action can enable drag but doesn’t disable it if triggered again. Thanks

image
image336×351 10.3 KB

4

Hi @alfocabezas37,

This change is just UI-side in Bubble - the action still supports enable/disable the same way as before, but Bubble now shows that “key/value pair array” as a single ID input.

To disable dragging, pass the pair in this format in the ID field:

  • disable=your_element_id

To enable it again:

  • enable=your_element_id

You can also disable/enable multiple elements at once by providing a list of these key=value entries (since that field is an array under the hood). This matches the current docs for Make Elements Draggable.

If it “re-enables” unexpectedly, that usually means the enable action is being triggered again by another workflow (or the same one re-fires). Put a tight Only when condition on the workflow and/or track a custom state like is_draggable so you only run enable=... once, and run disable=... when turning it off.

Also double-check the target element has its ID attribute set in Bubble (Settings → General → expose option) and that the ID matches exactly.

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3

5

I’m afraid using enable=your_element_idor disable=your_element_id doesn’t work. Drag is only enabled if I only fill the ID field with my element’s ID, adding enable= or disable= before makes it stop working altogether.

This doesn’t enable drag of team1 element:

image
image338×343 10.3 KB

This DOES enable drag of team1:

image
image336×350 10.2 KB

Same happens with ‘disabled’. For the moment I’ve found an alternative solution, when I want to disable that element’s drag I fill the ‘Parent id as limit’ field with the same element’s id.

6

Hi @alfocabezas37,

Yep - this is a bit picky, and your screenshots actually hint at the reason.

In this plugin, the action expects the pair in the exact key = value format (with spaces), not key=value. That’s also how it’s written in the docs: key = value where key is enable / disable, value is the element’s ID.

So please try exactly:

  • Enable: enable = team1
  • Disable: disable = team1

(No quotes, and make sure team1 is the element’s ID Attribute in Bubble.)

If enable = team1 still doesn’t work on your side, then we’re likely looking at a Bubble UI/input-type change (the field used to be a key/value array, now it’s shown as a single ID field), and we’ll need to reproduce it.

In that case, send us:

  1. Your plugin version (Settings → Plugins → Mouse & Element Positions + Move)
  2. A short Loom showing the workflow + the element’s ID Attribute

Your workaround with “Parent id as limit = same element id” makes sense as a temporary lock, but the proper disable should work via disable = ... once the input is passed in the expected format.

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3

7

Yes I’ve tried enable = team1 and disable = team1 with spaces, no result for both actions, the ID field is only accepting elements’ ids alone without key. I don’t mind enable because just typing the element id alone works fine to enable the drag, I just need a way to disable it and disable = ‘that same element’s id’ doesn’t disable drag.

image
image335×346 10.2 KB

8

Hi @alfocabezas37

Thanks for confirming (and for the screenshots).

If disable = team1 / enable = team1 doesn’t work even with spaces, and only the raw ID (team1) works, then Bubble is almost certainly passing only the value to the action (and dropping the “key” part). In other words: the workflow field UI changed, and the plugin no longer receives the enable/disable pair as intended — so disable can’t be triggered from that input right now.

Docs still describe it as a key/value array (enable or disable + element ID).

Practical workarounds (no custom code)

Use one of these until we patch/confirm the behavior:

  1. Your workaround is valid
    Set Parent id as limit = team1 (same element). This effectively locks the drag.
  2. Swap elements (clean UX)
  • Create two versions of the element:
    • A “draggable” one (ID team1)
    • A “static” one (no drag action applied)
  • Show/hide them with a condition / custom state (is_draggable).
    This avoids any drag listener issues entirely.

To get this fixed properly

Send us:

  1. Plugin version (Settings → Plugins → Mouse & Element Positions + Move)
  2. A short Loom showing the exact workflow action + what you type in the ID field
  3. (Optional but ideal) a live test page / editor link where we can reproduce

Once we can reproduce it, we’ll push a fix so the disable action works again from the workflow field.

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3

9

Hi @alfocabezas37,

Just following up on the issue you reported with disabling drag for an element.

We understand that the “disable = element_id” approach isn’t working, and that only the raw element ID enables drag. Could you kindly share:

  1. The plugin version (Settings → Plugins → Mouse & Element Positions + Move)
  2. A short Loom video showing the exact action and what you type in the ID field
  3. If possible, a live test page or editor link where we can reproduce this issue

Once we have those, we’ll be able to investigate further and get this fixed for you.

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3

10

version is 2.23.0. want me to fix the bug as well?

11

Hi @alfocabezas37,

There was a confusion in the format used in the docs — apologies for that.

The correct syntax is with a colon :, not =.

Please use:

  • team1:enable
  • team1:disable

So to disable drag for your element, enter:

team1:disable

Also, just a small note — this plugin works reliably inside a Fixed container (since it relies on absolute positioning). It may not behave correctly inside fully responsive layouts.

Please try the correct elementID:action format inside a Fixed container and let us know if everything works as expected now.

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3

12

Hi @alfocabezas37 ,

Just following up to see if using the correct elementID:enable / elementID:disable format has resolved the issue for you.

Let us know if it works as expected in the Fixed container, or if you need further assistance!

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3