1st Touch also must fire mouse events

[Philzen]

Looking at the SnappyMaria Touchtest, a native touch is also firing mousedown, mousemove, and mouseover events (testing on HTC Vision with 2.3.3)

These need to be fired by polyfilled Touches as well.

Questions:

1. Do android phones implementing native multitouch send those also on the 2nd, 3rd, etc... touch?
2. Are there android phones generating only some of the mouse events listed above or different ones or not at all for that first touch?
   Guessing if so, that would not be standard, as smartphone browsers need to provide a way to interact with the "classical" web.

[fastrde]

SnappyMaria Touchtest fires only touchstart, -move, -end on my device (Samsung Galaxy S II with 2.3.3) while touching the surface with one finger in the OS Webbrowser, Firefox and Opera mobile.

[Philzen]

Did you test WITH polyfillAllTouches = false !? If that's really true i'm wondering how browsing desktop pages/apps with the phone could ever work - that was my understanding that they need to be there for that reason. I tried some classical drag and drop web pages with polyfillAllTouches = true on mine and all of them are unusable (no mousedown = no interaction possibility)

[fastrde]

you are right. Didn't test it with polyfillAllTouches = false. But tested it within different browsers... so the TestActivity was not involved all time. Will test it again.

[Philzen]

Great, will see if i can get my hands on any iPhone or Android 4 to shed some light on Question 1 in the meanwhile.

I am wondering if there is an easy way to send a mail to all watchers or add them to the discussion so they can help out with their devices... also thinking of posting an open call for support into the OpenLayers and PhoneGap mailing lists.

[Philzen]

I'm flabbergasted... just checked the touch test on an iPhone 4: there are also no mouse events being emulated by neither the 1st or any following touches.

So - if that also holds true on the samsung s II, it means that this is some proprietary HTC ("it's not a bug, it's a ...") feature. What on earth could have been the intent for HTC to do such a thing?

When confirmed, the issue can be closed, but i guess makes a lot of sense to make polyfillAllTouches = false the default setting for the next minor release, so any of this quirky, proprietary implementations (which may or may not have a good reason to exist) will not be changed when using WMP

[fastrde]

Tested now on

• T-Mobile G1 (Android 1.6) => Only Touch Events and only one touch simultaneously
• Samsung Galaxy S II (Android 2.3.3) => Only Touch Events and only one touch simultaneously

[fastrde]

Some friends of mine tested too:

• HTC 7 Mozart (Windows Phone 7.5) => Only Mouse Events and only one touch simultaneously
• IPhone 4 => Only Touch Events
• IPad 2 => Only Touch Events
• Samsung Galaxy S i9000 (Android 2.3.5) => Only Touch Events and only one touch simultaneously
• Samsung Galaxy S+ i9001 (Android 2.3.6) => Only Touch Events and only one touch simultaneously

[Philzen]

Fixed in commit cab0519

This change apparently will help to avoid many problems such as Philzen/cordova-android-multitouch-polyfill#2, i actually have seen similar on some of my apps.

To be included in the v0.3 tagged release