18 Jul 2012 12:00 AM #1
error on drag and touch move events in Chrome on windows touch screen devices
When using the google chrome browser on windows 7 or windows 8 with a touch screen, the "drag" and "touch move" events are not fired. Use the kitchen sink touch events example as repro.
Sometimes I can get the events to be fired by doing a fast single tap directly before doing the actual drag tap. Weird.
It works perfectly on safari though...
Any clue why this behaviour occurs?
18 Jul 2012 5:25 AM #2
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
In chrome have you enabled the emulate touch events setting?Mitchell Simoens @LikelyMitch
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services email@example.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.
18 Jul 2012 6:25 AM #3
20 Jul 2012 7:07 AM #4
26 Jul 2012 2:57 AM #5
are there any news on this issue? do you need any more information?
it's a pretty crucial point for our product as we aim to recommend larger windows 7/8 touch screens to our customers...
24 Aug 2012 11:08 PM #6
hello, any news on this?
can't there anyone at sencha reproduce this and say whether you will be able find a fix or not...?
REPRO: just start the kitchen sink example on a chrome browser and windows7/8 touch screen... and try to tap-scroll
18 Dec 2012 3:05 AM #7
Same problem here!
Windows 7, Chrome 23, HP touchscreen, Sencha touch 2.0.1.
The carousel kitchensink example for Sencha touch 2.1 isn't working either. Can swipe with the mouse, but not with the touchscreen.
25 Jan 2013 2:55 AM #8
any news on this? please don't let us alone here! i would be glad just for a simple answer...
8 Feb 2013 10:09 AM #9
Blocker for us
... this is a blocker for us in using Sencha Touch on large surface / table solutions. Any info at all?
Repro'ed on Sencha Touch 2.1.1 + Chrome 24
8 Feb 2013 5:33 PM #10
Cause & workaround
I now believe that these issues is caused by a recently introduced chrome feature, 'Force enable touch events'. I found the description of this new feature, introduced Aug '12, here.
The good news is there is a workaround, the 'bad' news is it requires non-stable chrome install.
As I understand, read: from my experimenting, these chrome-interpreted touch events need to be disabled in order for the current windows secha touch to work. Stable chrome only allows you to autodetect ('Force enable touch events' in about:flags disabled) or to enable (that flag enabled). So with an actual touch device you are forced to have these effectively enabled, and sencha touch will not work as expected.
Chrome Canary build 26.0.1407.0 (and hopefully earlier beta/dev streams? confirm pls) have a triple-dropdown for enable/disable/automatic. Setting it to disable... disables it! And voila problem 'solved'.
I hope that support staff has done their homework on this at least for the premium members...