Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarifying handedness #125

Merged
merged 2 commits into from
Jun 5, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions explainer.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ This API will only be accessible if a `"hand-tracking"` [XR feature](https://imm

This API presents itself as an additional field on `XRInputSource`, `hand`. The `hand` attribute will be non-null if the input source supports hand tracking and the feature has been requested.

You can determine which hand the input source is associated with by accessing the `handedness` property of `XRInputSource`.

```js
navigator.xr.requestSession({optionalFeatures: ["hand-tracking"]}).then(...);

Expand Down
2 changes: 2 additions & 0 deletions index.bs
Original file line number Diff line number Diff line change
Expand Up @@ -256,6 +256,8 @@ The {{XRHandJoint}} enum defines the various joints that each {{XRHand}} MUST co

Every {{XRHand}} has an associated <dfn for=XRHand>input source</dfn>, which is the [=physical hand input source=] that it tracks.

NOTE: The <code>handedness</code> property of {{XRInputSource}} describes which hand the XR input source is associated with, if any.

<div algorithm="XRHand.[[joints]]">
Each {{XRHand}} object has a <dfn attribute for="XRHand">\[[joints]]</dfn> internal slot,
which is an [=ordered map=] of pairs with the key of type {{XRHandJoint}} and the value of type {{XRJointSpace}}.
Expand Down
Loading