feat(XR): Handle WebXR XRInputSourceEvents #2221
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR and Code Checklist
npm run reformat
to have correctly formatted codeContext
The WebXR API exposes a limited number of user input events, which we expose to the user here through
RenderWindowInteractor
alongside other typical browser events.Note that the granularity offered through XR events does not match that of the XR gamepad API, through which we can query continuous values such as touchpad or joystick position through our
updateXRGamepads
method. Developers should take both approaches into account.Changes
RenderWindowInteractor
.Results
Exposes six new events ("select"/start/end, "squeeze"/start/end) that developers can choose to handle.
Testing
master