error on drag and touch move events in Chrome on windows touch screen devices

[jensen83]

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?

[mitchellsimoens]

In chrome have you enabled the emulate touch events setting?

[jensen83]

no, it's not enabled.

[anj]

same problem here

[jensen83]

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...

[jensen83]

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

[Sander77]

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.

[jensen83]

any news on this? please don't let us alone here! i would be glad just for a simple answer...

[msowka]

... 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

[msowka]

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...