onTouchStart results in unexpected behavior

With this line in place, merely scrolling past the image gallery with the scrolling finger touching the area of the gallery will result in the triggering of the custom onClick method, which, in turn, might do things like opening a larger image on a modal; a very unexpected behavior and frustrating user experience.

The onClick should trigger just fine on tap events on touch devices, there is no need to specify a separate onTouchStart if the goal is simply to make sure that the custom onClick method works on these devices. Is there any other reason for having included this line, or is it safe to remove it?

[xiaolin]

Ah, okay. I’m going to close this issue then. Thanks!

[gaborluk]

No, scrolling happens properly regardless of being initiated on one of these elements or not, I was just commenting on the control handlers firing as a side-effect of scrolling, and not as an intended action in these cases. As I’ve said, this is a much less serious issue than the custom onClick handler firing on the main image’s touchstart, ultimately you’re juggling two similarly frustrating mobile UX concerns, of which keeping one or the other will have to be a fairly subjective decision, so it’s really up to you. I’m already happy with the original issue being taken care of.