Hmm, is your drageable element a child element? If yes then instead of half of the page width, try half of the parent element’s width.
I experienced the same thing for my app (which is designed for desktop use first) and this fix works for me but it does have some quirks depending on the parent-child layout.
It’s not a bug persay as the offset is very consistent so it’s about figuring out what works for your situation.
Did you have any joy with getting the ‘Tab’ key to work within the interactions for key press. I’ve tried just about everything, copy/pasting conditions in to try and get the ‘Tab’ in, like you said, if you continue pressing, it will briefly be visible but wont actually save to the expression composer.
A gave up on getting any response from Bubble on this, and I’m now using a plugin called Keystroke Input Trigger. It’s a bit clunky and I hate to rely too much on third party plugins, so I’m pretty much just waiting for Bubble to wake up. Keyboard shortcuts is a pretty essential feature for productivity apps, which is what I’m developing.
Who to tag to have someone look into this again? It’s been an experimental feature for more than 2 years…
Yeah I didn’t think would be experimental still, but seems the case to be honest - hopefully not an abbonanded project as it has massive potential to expand upon UX interactions and such.
Thanks for the reply though. Will see what happens and maybe use something else rather than the native solution
@allenyang It looks like this plugin has been abandoned. This shouldn’t be a “highly experimental” feature as accessibility laws require keyboard navigation. This is not only necessary from a product perspective, but also a legal one. Thanks!
There now doesn’t seem to be an option to add the necessary only when conditions to the top level of the ‘left mouse button clicked down’ workflow (existing workflows still function but cannot be edited) - unless I am imagining this was once an option?
+1 for getting this updated and out of experimental mode - and 18,015 apps agree!
Yeah, I’m quite surprised that this has not been addressed yet.
In general Bubble is not that great for productivity apps where features like keyboard shortcuts and drag-n-drop are essential. But I’m currently still finding myself brute forcing my way through it with home cooked plugins and workarounds Time will tell if this was a good decision or not.
I want to bring some attention to this as our app also relied heavily on keyboard shortcuts. @fede.bubble Do you have any insights into why we can’t add conditions to the actions anymore?