Skip to content

Indicate the preferred ergonomics of a tracked-pointer ray #524

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

Merged
merged 2 commits into from
Feb 25, 2019

Conversation

toji
Copy link
Member

@toji toji commented Feb 14, 2019

Fixed #516.

@toji toji requested a review from NellWaliczek February 15, 2019 00:03
@toji
Copy link
Member Author

toji commented Feb 25, 2019

Review ping: Anything else you'd like to see changed before landing?

@@ -1067,7 +1067,7 @@ The <dfn attribute for="XRInputSource">handedness</dfn> attribute describes whic
The <dfn attribute for="XRInputSource">targetRayMode</dfn> attribute describes the method used to produce the target ray, and indicates how the application should present the target ray to the user if desired.

- <dfn enum-value for="XRTargetRayMode">gaze</dfn> indicates the target ray will originate at the user's head and follow the direction they are looking (this is commonly referred to as a "gaze input" device).
- <dfn enum-value for="XRTargetRayMode">tracked-pointer</dfn> indicates that the target ray originates from either a handheld device or other hand-tracking mechanism and represents that the user is using their hands or the held device for pointing.
- <dfn enum-value for="XRTargetRayMode">tracked-pointer</dfn> indicates that the target ray originates from either a handheld device or other hand-tracking mechanism and represents that the user is using their hands or the held device for pointing. The orientation of the target ray relative to the tracked object MUST follow platform-specific ergonomics guidelines when available. In the absence of platform-specific guidance, the target ray SHOULD point in the same direction as the user's index finger if it was outstretched.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the target ray SHOULD point in the same direction

Any reason why this isn't a MUST either?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's feasible that the UA has a tracked device that it knows the position and orientation of but no sense of how it's actually shaped, in which case it's difficult to comply with a MUST here.

@toji toji merged commit 1e5bae3 into master Feb 25, 2019
@toji toji deleted the spec-target-ergo branch February 25, 2019 23:07
@AdaRoseCannon AdaRoseCannon added the ed:spec Include in newsletter, spec change label Mar 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ed:spec Include in newsletter, spec change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants