Intent to Prototype: GamePad multitouch extension

[Bradley Needham]

Contact emailsmattre...@chromium.org

Explainerhttps://github.com/bradleyneedham/gamepad/blob/multitouch-explainer/multitouch_explainer.md

Specificationhttps://knyg.github.io/gamepad/extensions.html#gamepadtouch-interface

Summary

Extend the Gamepad API to support multitouch surfaces (touchpads). Providing a touchpad API eases application implementation and provides greater functionality browser interoperability.

Blink componentBlink>GamepadAPI

Motivation

Gamepad Multitouch Extension Provide access to the touch interface available on modern gamepads by allowing developers to receive touch events generated by the gamepad. Modern gamepads support touch functionality, e.g. Sony DualSense®5, Steam deck and Steam Controllers, and Sony DualShock®4. The Standard Gamepad specification should be updated to include touchpad functionality, and the Gamepad API should be extended so that users with touch-enabled gamepads can use touch inputs on the web.

Initial public proposalhttps://github.com/w3c/gamepad/issues/34

TAG review

TAG review status

Pending

Risks

Interoperability and Compatibility

Gecko: No signal

WebKit: No signal

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

Debuggability

n/a

Is this feature fully tested by web-platform-tests? No

Flag name

Requires code in //chrome?False

Tracking bughttps://crbug.com/1143942

Launch bughttps://crbug.com/1372607

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Statushttps://chromestatus.com/feature/4782975812108288

Links to previous Intent discussions

Intent to prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/cMoPvrdcF0E/m/YNB44fMgAAAJ

This intent message was generated by Chrome Platform Status.

[Alex Russell]

This seems like a valuable extension, and something that I'd love for TAG feedback to be solicited on sooner rather than later, as we have a lot of precedent in the platform for multitouch inputs (e.g., Pointer Events API), and it would be great not to create incompatible types and techniques for handling them, particularly given that there's effort ongoing to implement the event-driven style of gampead API (IIRC).

Best,

Alex

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/d19b95b3-1b42-4d2b-9ff0-587d6568dfd6n%40chromium.org.

[Rick Byers]

Looks like a TAG review has been filed here: https://github.com/w3ctag/design-reviews/issues/799

FWIW, I was thinking the same thing, and was a little alarmed to see something new called a "touch event" :-).  But after reminding myself of the history of the PEWG design discussions and looking at the proposed spec, I personally think the proposal is fine. Happy to discuss further in the TAG issue or elsewhere if desired.

Rick

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAA44PQjCdPVcc2KUC-rDEA4m-v6z9aEp-fpacsk09%3Dfyp6vesg%40mail.gmail.com.