A-frame 1.2.0 custom cursor stopped rendering properly on iOS all iphones
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
Description:
- A-Frame Version: 1.2.0
- Platform / Device: iOS (all iPhones)
- Reproducible Code Snippet or URL: https://tours-staging.3destate.pl/testowa-ttdh/4.3d <-- click menu, then VR and it appears, function that added cursor is:
addGazeCursor: function () {
const camera = document.getElementById('camera');
camera.removeAttribute('raycaster');
camera.removeAttribute('cursor');
const cursor = document.createElement('a-entity');
cursor.setAttribute('fuse-cursor-loader-animation', {});
cursor.setAttribute('id', 'cursor');
cursor.setAttribute('position', '0 0 -2');
cursor.setAttribute('raycaster', { objects: '.clickable', far: 5000 });
cursor.setAttribute('cursor', { fuse: true });
cursor.setAttribute('geometry', { primitive: 'ring', radiusInner: 0.01, radiusOuter: 0.02 });
cursor.setAttribute('material', { color: '#898989', shader: 'flat' });
camera.appendChild(cursor);
},
It was all god on 1.1.0 and previous, but on 1.1.0 Android VR doesnt work properly... we actually were using 1.0.4 without Android chrome 80+ VR support, and now we wanted to check how is it after updates, with 1.2.0 android started to work properly, but not an iOS anymore :( would be great if you could help me with that!
Issue can be somewhere in geometry or polyfills?
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 reproducing the issue at the linked test URL on iOS, then inspect the addGazeCursor function and compare behavior between A-Frame 1.2.0, 1.1.0, and 1.0.4. Done means the custom cursor renders correctly on iPhones while preserving the Android VR behavior described in the report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ar-vr-xr
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100