ZIM tap() now defaults to mousedown on Mobile

Announcements
,
1

CHANGE
ZIM tap() now defaults to mousedown on Mobile. We have added a mobileUp parameter at the end of tap() that can be set to true to return to a full up and down.

REASONING
Tap is very handy, but previously, we would not use it for mobile because the down and up makes interactions on mobile seem sluggish.

WATCHOUT
We use tap() with mobileUp automatically for List() where we purposely do not activate list change on mousedown - because then swiping the list would also activate a selection. So any interactivity like this that you have in your apps - make sure to note the change in tap() for mobile.

1 Like
4

Hello.
this.tap(e => {
window.open(this.link, "_self")
}) What should I do for the function I use in this way on mobile? What should I do to prevent it from being confused with pressmove?

5

Is there a need for a change in the default on mobile? Is it okay if we continue to use mousedown and pressup on mobile?

6

You can certainly use mousedown and pressup events as you like. This is the tap() short chainable method. It will default to mousedown on mobile and pressup not on mobile.

7

As far as I understand, pressup is not triggered only on mobile. To trigger this, we will set mobileUp to true.

8

When you use tap() and want it to activate on pressup for mobile - yes, you need to set mobileUp to true.

This announcement is specifically only for tap(). All the on() events work the same as before.

1 Like