Javascript events being ignored until the scene is touched.
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: 0.8.2
- Platform / Device: Android and iOS touch devices
- Reproducible Code Snippet or URL: http://reslife360.blackswaninteractive.com/main-aframe-0.8.2.html
We are having an issue where two buttons that our outside of the aframe scene are being used to lad a new template in the scene. This works great on a desktop with a mouse, but on a touch device, either iOS or Android the button doesn't load the new scene, it just refreshes the current one. If, however, you tap the scene at all before clicking the button it works as expected.
An easy way to reproduce this is to click the link above > Founders Hall > click on the back button in the bottom left (same scene will refresh)
However click the link above > Founders Hall > tap anywhere on the scene > click on the back button in the bottom left > you'll return back to the previous scene
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 with the linked reproduction at reslife360.blackswaninteractive.com/main-aframe-0.8.2.html and follow the Founders Hall and back-button steps on Android or iOS. Compare the button behavior before and after tapping the A-Frame scene; done means the external buttons load the intended scene without requiring a prior scene tap.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100