[w3c/gamepad] Determine how Multi-touch surfaces should be handled. (#27)

As of https://github.com/w3c/gamepad/pull/26 the gamepad API now supports single touch touchpads and similar capacitive controls. That addition to the spec does not (explicitly*) cover multitouch surfaces, however. It also doesn't cover more complex touch concepts like gestures. It seems like if we want to take advantage of increasingly complex touch surfaces a more robust API is needed, along the lines of PointerEvents (or even using PointerEvents directly).

That being said, the number of gamepad-like objects that have multitouch surfaces is pretty low. The only ones I know of off the top of my head are the PS4 controller (who's touchpad is limited to 2 touch points) and the WiiU Pad which... just, no.

*It's possible that you could represent a multitouch control with multiple pairs of axes and multiple buttons to represent each touch point, but that feels like it's stretching the API a bit thin.


---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/27