Sorry for the delay, for some reason these notifications always go to my junk folder.
@mhartington that’s correct, part of the problem is that when a user “taps”, their finger stays on for a little bit longer than the default threshold (any idea what that is or if that is configurable?) the ripple animation starts but the action does not trigger. This one we can reproduce on Android quite frequently.
Another part, sometimes what seems like a real tap also triggers the animation but doesn’t trigger the action. For this one, my guess is that the touch screen might be registering some other type of event like a short pan/drag/swipe instead of a true 100% tap, which could be due to screen sensitivity etc.
Regardless, I believe these should still trigger the action bound since the touchstart was triggered.
Any idea if there’s a way to configure all of these events to still trigger the action bound to the button or tweak the thresholds?
Do you think there is a way to use @HostListener(‘touchend’) with an ion-button as a workaround for sensitive buttons in the meantime (i.e. for those buttons that are critical and have to be triggered in all of the above touch-types)?
@Daveshirman, I agree regarding user expectations. As for the testing on iOS tablets, I take your word for it. The apps my team worked on are mainly enterprise custom apps deployed on Android. Have you been able to experiment with touchend at all or have you seen this issue with using simple html buttons (i.e. do you see the same behaviour with using <button …>) ?
Thank you both for your help with this.