Section 3.2.1: Improvements for game pad input

[aboba]

In previous discussion, it has been pointed out that the Game Pad API (see: https://w3c.github.io/gamepad/ ) is not easily integrated with WebRTC-based cloud gaming applications. This issue is being filed to track the specific requirements that would address current limitations.

[dontcallmedom-bot]

This issue was mentioned in WEBRTCWG-2023-05-16 (Page 14)

[aboba]

I believe that this issue might be addressed via Game Pad API extensions such as Gamepad Axis and Button Events
PR: w3c/gamepad#152
Chrome implementation tracking bug: https://bugs.chromium.org/p/chromium/issues/detail?id=856290

Problem: The Game Pad API and the proposed extensions do not appear to relate to transport or media processing, so it is not clear that they are in scope for the WebRTC WG, or even related WGs such as MEDIA WG or WebTransport WG.

[dontcallmedom-bot]

This issue had an associated resolution in WebRTC July 2023 meeting – (Issue #94: Improvements for game pad input (Section 3.2.1)):

RESOLUTION: Send an email to the gamepad people and ask what's going on, but do not change document.

[dontcallmedom-bot]

This issue was mentioned in WEBRTCWG-2023-09-12 (Page 27)

[dontcallmedom-bot]

This issue was mentioned in WEBRTCWG-2023-12-05 (Page 19)