Quantcast
Channel: Appcelerator Developer Center Q&A Tag Feed (android)
Viewing all articles
Browse latest Browse all 7655

touchmove/touchcancel problem on Android - touchcancel is firing too soon

$
0
0

On Android, touchmove is being interrupted by touchcancel. Also, once the touchcancel event has fired, the touchend event never gets fired either (which is the correct behavior - assuming the touch cancel event is being fired correctly).

The interesting thing is that iOS also fires the touchcancel event prematurely (you can test this by updating a label when the touchcancel event fires), however, it seems iOS is clever enough to realise that the user is still "touchmoving" on the screen and it keeps firing the touchmove event regardless of whether or not the touchcancel event was fired. It seems to me that this is actually a bug, but thanks to this bug, it works on iOS.

I'm using Ti Studio with SDK version 2.1.3.GA

I've tested this on both the V8 and Rhino Android Runtimes (as seen in the tiapp.xml editor)

I must say, this is really disappointing. One would think that for touch enabled devices, getting the touchmove/touchcancel events working properly would be one of the core issues to deal with?

I've also tried the TiDraggable module (https://github.com/pec1985/TiDraggable/), however, the behavior is identical.


Viewing all articles
Browse latest Browse all 7655

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>