Same here, on Android Chrome. The JS script that the author is using relies on listening to both mousedown and touchstart events, etc. It isn't clear to me why

Same here, on Android Chrome. The JS script that the author is using relies on listening to both mousedown and touchstart events, etc. It isn't clear to me why Android has a problem with that, but I wonder if switching to listening only for pointer events [1] would fix things. [1] https://developer.mozilla.org/en-US/docs/Web/API/Pointer_events https://developer.mozilla.org/en-US/docs/Web/API/Pointer_eve...