I hope I am doing something wrong but I'm afraid this is as intended and would love to hear your opinion.
Adobe XD V: 184.108.40.206, CCS: 220.127.116.11, Windows 10
Horizontal scroll container, elemenets within it have a tap trigger to a new artboard.
When the prototype is running, releasing my tap / click will trigger the tap trigger. This results in use errors while swiping - like everytime.
Normally having a tap trigger fire on release instead of "tap motion" (or even worst: on touch) is a pretty good practice. But this normally has to be coupled with a time-buffer. This way you get the biggest freedom of use and those "finger down on a button - uuuuh wait - sliding off button - avoiding the user error"-moments. But how it is at the moment it is the exact opposite: swiping - ariving over button - letting go of the slide motion - triggering tap trigger "on release" = use error. I mean starting a touch outside of the button and releasing it on a tap trigger really doesn't sound like intended or am I simply doing something wrong here?
Any help, advice or discussion is greatly appreciated 🙂
Have a great day!
Copy link to clipboard
Hi Chris, would you be able to send us the prototype link?
Maybe just the "naked" elements if it's confidential? It would be useful to see what the exact situation is.
Also, a screenshot from Xd on the prototype tab with the artboards selected, so we can see the links would be nice as well.
Hi Spas K.,
thank you so much for your reply.
Here is a "naked" prototype (includes instructions on how to reproduce).
In Short: Try using the horizontal swipe gallery without use errors 😄
And a screenshot with the links and the trigger "tap" selected.
Any opinion on this behavior? I'm pretty sure I used horizontall scroll containers in the past like this wihtou this issue. Is this maybe a bug indeed?
Okay, I see what you mean. Definitely seems like a bug. A click/tap should never register on release, if you have moved the cursor between pressing and releasing the mouse button. It seems to be happening on the whole prototype. Whenever you click and drag anywhere on the page, a click is registered upon releasing the mouse button.
It only happens when you open the prototype in a desktop browser and try to "swipe" with the mouse cursor (click & drag). It doesn't happen when I open the prototype on my phone and do the same thing. There was a similar issue, although different, when the scroll areas were first released.
@HARSHIKA_VERMA can you confirm whether this is a known issue, or maybe it should be filed as a bug?
To reproduce - on a prototype, press and hold the mouse button anywhere on the page, drag the cursor over an active element (like a button), and then release the mouse button. This shouldn't register as a click, but it does. This happens in the browser, or the prototype view screen in Xd. Only on desktop. On mobile it works as intended.
Thanks for flagging this out. I tested this on my end and I am able to reproduce this so I'll log a feedback ticket and will update this discussion as soon as I hear from the team.