Copy link to clipboard
Copied
I made a simple carousel in an element, changing it's position between two artboards.
I create the drag interaction, but the element earns a tap interaction, but this one wasn't set in any moment.
I think it may be a bug.
I can confirm your conclusion.
Setting an freshly made interaction to the intended Drag trigger, invokes an unwanted Tap trigger doing a Transition. And it's not possible to set the trigger beforehand (it remains gray), or to remove the Tap trigger by setting the Destination to None afterwards, and then reselect and reset the Drag trigger. There will always remain a Tap trigger...
This is clearly a flaw in the design of the feature.
We must wait for the developers to correct and improve it, an
...Copy link to clipboard
Copied
Hi Francobits,
You really make good designs in Adobe XD. Would you mind sharing the screenshot of the design showing all the interactions in the prototype mode? I would also like to confirm if you have connected the second scroll back to the first one.
Please check out this post for Horizontal Scrolling in Adobe XD: https://community.adobe.com/t5/adobe-xd/horizontal-scrolling-in-adobe-xd/td-p/10602069?page=1
Let us know if that helps.
Thanks,
Harshika
Copy link to clipboard
Copied
I understand the intended scenario, and see that it's going wrong. I created a similar setup, and it works like it should. So there must be something wrong in your version. Without any hands-on, I can only look at your example in the same puzzled state like you. Are you willing to share the file ?
Copy link to clipboard
Copied
Hey guys, thank you for your feedback. While I was preparing the files to upload for you, I guess I discovered the bug. When I have a scrollable artboard and the drag trigger is below the viewport line, it "adds" a tap interaction.
I created a new, simpler file with only two scrollable artboards and a drag interaction between them.
https://downloads2.nddigital.com.br/franco/scroll-drag-bug.zip
Copy link to clipboard
Copied
I can confirm your conclusion.
Setting an freshly made interaction to the intended Drag trigger, invokes an unwanted Tap trigger doing a Transition. And it's not possible to set the trigger beforehand (it remains gray), or to remove the Tap trigger by setting the Destination to None afterwards, and then reselect and reset the Drag trigger. There will always remain a Tap trigger...
This is clearly a flaw in the design of the feature.
We must wait for the developers to correct and improve it, and the marketeers to claim it as a break-through new feature...