Page 1 of 2 12 LastLast
Results 1 to 10 of 12

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

    Wait! Looks like we don't have enough information to add this to bug database. Please follow this template bug format.
  1. #1
    Sencha Premium Member
    Join Date
    Aug 2010
    Posts
    27
    Vote Rating
    1
      0  

    Default 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?

  2. #2
    Sencha - Sr Software Engineer mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    39,422
    Vote Rating
    1271
      0  

    Default

    In chrome have you enabled the emulate touch events setting?
    Mitchell Simoens @LikelyMitch
    Sencha Inc, Senior Software Engineer
    ________________
    Learn BBCode and use it!

    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    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 services@sencha.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.

  3. #3
    Sencha Premium Member
    Join Date
    Aug 2010
    Posts
    27
    Vote Rating
    1
      0  

    Default

    no, it's not enabled.

  4. #4
    Sencha User
    Join Date
    Mar 2007
    Posts
    18
    Vote Rating
    2
      0  

    Default

    same problem here

  5. #5
    Sencha Premium Member
    Join Date
    Aug 2010
    Posts
    27
    Vote Rating
    1
      0  

    Default

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

  6. #6
    Sencha Premium Member
    Join Date
    Aug 2010
    Posts
    27
    Vote Rating
    1
      0  

    Default news?

    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

  7. #7
    Touch Premium Member
    Join Date
    Aug 2011
    Posts
    1
    Vote Rating
    1
      1  

    Default

    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.

  8. #8
    Sencha Premium Member
    Join Date
    Aug 2010
    Posts
    27
    Vote Rating
    1
      0  

    Default

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

  9. #9
    Sencha Premium Member
    Join Date
    Jan 2010
    Posts
    5
    Vote Rating
    0
      0  

    Default 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

  10. #10
    Sencha Premium Member
    Join Date
    Jan 2010
    Posts
    5
    Vote Rating
    0
      0  

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

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •