Rotating phone from portrait to landscape mode while loading results in bad starting direction
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
I've been able to reproduce this 100% of the time on both my project and projects online, on multiple phones.
To reproduce it, make sure "Auto-Rotate" is set to ENABLED on your phone, then start an A-Frame game
During the loading screen (with the animated dots), rotate your phone to landscape mode.
When the loading will finish, the starting direction will be offset, meaning that you will have to rotate to face the default starting area.
Here is a screenshot of what I mean
- A-Frame Version: 1.3.0
- Platform / Device: Android
- Reproducible Code Snippet or URL: I could successfully reproduce the bug here as well: https://aframe.io/aframe/examples/showcase/shopping/
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
Reproduce the issue in the linked A-Frame shopping example on Android, following the loading-screen and portrait-to-landscape steps. Start by locating the loading and mobile orientation handling; done means the default starting direction remains correct after rotation during loading, with a regression test covering the scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- mobile-dev, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100