Duplicate pinch events on the Quest Pro
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
Performing a single pinch emits multiple "pinchstarted" and "pinchended" events on the Quest Pro (I don't have any other headsets to test this on). Here's a video of the issue comparing A-Frame 1.5.0 and 1.4.0
- A-Frame Version: 1.5.0
- Platform / Device: Quest Pro
- Reproducible Code Snippet or URL: glitch code and the live version
<html>
<head>
<title>A-Frame pinch issue on Quest Pro</title>
<script src="https://aframe.io/releases/1.5.0/aframe.min.js"></script>
</head>
<body>
<a-scene>
<a-entity id="rightHand" hand-tracking-controls="hand: right;"></a-entity>
<a-camera>
<a-entity position="0 0 -1">
<a-text
id="numberOfPinches"
color="black"
align="center"
value="0 pinches"
></a-text>
<a-plane color="white" position="0 0 -0.01" height="0.3" width="1.1"></a-plane>
</a-entity>
<a-sky hide-on-enter-ar color="grey"></a-sky>
</a-camera>
</a-scene>
<script>
const rightHand = document.getElementById("rightHand");
let numberOfPinches = 0;
const numberOfPinchesEntity = document.getElementById("numberOfPinches");
rightHand.addEventListener("pinchstarted", (event) => {
numberOfPinches++;
console.log({ numberOfPinches });
numberOfPinchesEntity.setAttribute(
"value",
`${numberOfPinches} pinches`
);
});
</script>
</body>
</html>
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the linked Glitch reproduction on a Quest Pro and compare A-Frame 1.5.0 with 1.4.0, focusing on pinchstarted and pinchended dispatch. Done means one physical pinch emits one start and one end event; the issue does not name source files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100