New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 629101 link

Starred by 10 users

Issue metadata

Status: Duplicate
Merged: issue 830140
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Task
Launch-Accessibility: NA
Launch-Legal: NotReviewed
Launch-M-Target: 55-Dev , 55-Beta
Launch-Privacy: Started
Launch-Security: NotReviewed
Launch-Test: NotReviewed
Launch-UI: NA

Blocked on:
issue 628417
issue 644797
issue 644798



Sign in to add a comment

Gamepad API additions: Touched and Pose

Project Member Reported by bajones@chromium.org, Jul 18 2016

Issue description

Change description:
Add a couple of properties to the Gamepad API: a "touched" property for GamepadButton to explicitly support touchpads and a "pose" object on the Gamepad itself to support devices with accelerometers and 3 or 6 degree of freedom tracking. Our immediate interest in these new properties it to support VR controllers such as the Daydream controller, Vive wands, and Oculus Touch, but they are also be applicable to a wide variety of more traditional gamepads. 

Changes to API surface:
 * "touched" boolean added to GamepadButton
 * "pose" object added to Gamepad
   * includes 6 Float32Arrays, each representing a vector or quaternion: position, orientation, linearAcceleration, linearVelocity, angularAcceleration, angularVelocity.

Links:
Public standards discussion:
https://github.com/w3c/gamepad/pull/26
https://github.com/w3c/gamepad/pull/25

Support in other browsers:
Internet Explorer: No
Firefox: No
Safari: No

*Make sure to fill in any labels with a -?, including all OSes this change
affects. Feel free to leave other labels at the defaults.

 

Comment 1 by owe...@chromium.org, Aug 25 2016

As data exposed by accelerometers can be non-trivial from a security perspective please ensure you get a security review for the pose object before enabling the implementation. Thanks!

Comment 2 by f...@chromium.org, Aug 26 2016

Cc: f...@chromium.org
Is this actually targeted at M54?
Labels: -Launch-M-Target-54-Stable
Labels: -Pri-3 -M-54 Launch-Accessibility-NA Launch-Legal-NotReviewed Launch-M-Target-55-Dev Launch-Privacy-NotReviewed Launch-Security-NotReviewed Launch-Test-NotReviewed Launch-UI-NA Pri-2
Blockedon: 628417
Labels: -Launch-Privacy-NotReviewed -Pri-2 M-55 Launch-M-Target-55-Beta Launch-Privacy-Started Pri-1
Blockedon: 644797
Blockedon: 644798

Comment 9 by owe...@chromium.org, Sep 12 2017

Labels: migrated-launch-owp Type-Task
This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues.

We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate.

For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit

For any questions, please contact owencm, sshruthi, larforge
Components: Blink>GamepadAPI
Mergedinto: 830140
Status: Duplicate (was: Assigned)
https://www.chromestatus.com/feature/5651469617332224 tracked this functionality.

This issue is obsolete as VR-specific inputs, including pose, will be handled by WebXR Device API: https://github.com/immersive-web/webxr/blob/master/explainer.md#input

 Issue 830140  tracks enabling the `touched` attribute by default.
Labels: Proj-VR

Sign in to add a comment