Touch events not taken into account when both mouse and touch are available on device

[jmvie5]

Description:

On devices with multiple pointer devices (mouse and touch screen), the touch will not fire the MouseEvents (i.e. mousedown).

This is an issue for us when working with clients who use our web app with an interactive whiteboard connected to a computer. It seems like the computer's mouse is detected, but the touch events are not taken into account.

We experienced the same issue with a laptop with a touch screen; only mouse interactions worked, not touch screen interactions.

Reproduction:

Test Environment

If you have a laptop with a touch screen, click on the above link and try to manipulate the flowers with the touch screen. It does not work (at least on the machines I tested).

If you don't have a touchscreen laptop, open DevTools and use the simulate touch tool. Reloading the window with simulate touch enabled makes it work. However, if you first load the page without simulate touch and then switch to it without reloading the page, it does not work.

In the images, check the top right corners:

1. (works)

2. (Does not work, but will if you reload the page with this setting).

[jmvie5]

Did some testing and found that this fork resolves the issue.

Could you please merge this pull request : #1073 ?

[danzen]

Thanks @jmvie5 - we have just updated createjs.Touch. Sorry for the delay.

fec3159

This includes code that we have been running in ZIM since 2021 to solve touch screen issues. Some of which could be found in the pull request you mentioned. We have recently revisited our touch code as we got many reports from people with Prometheus boards. This led us to do research and we found the issue and confirmed it with Prometheus. If you are interested in reading the history there, please see https://forum.zimjs.com/t/pointer-events-support/4335 including status across BENQ, Wacebo, SMART, Promethean and Viewsonic boards. We have already tested various tablets, phones, desktop touch screens, etc.

[jmvie5]

Thank you very much @danzen for the response and the fix. We weren't sure if CreateJS was still being maintained, so we fixed our own version of it with your code we found in the PR above. We will look into using the official repo again.