Android: navigation bar no longer auto-hides
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Is there an existing issue for this?
- This is a bug in RetroArch frontend
- I have searched the existing issues
Description
Since version 1.18.0, the navigation bar no longer auto-hides after being accidentally shown. The only way to hide it is by going to home screen then return back to the application. Here is a screencast demonstrating this issue:
https://github.com/user-attachments/assets/504df1c9-69cf-4297-af07-d05f97313d3f
Expected behavior
The expected behavior is like the one in version 1.17.0 where navigation bar will auto-hide itself.
https://github.com/user-attachments/assets/619703c7-a715-4056-8a3c-0560b2f6f065
Steps to reproduce the bug
- Use Retroarch version >=1.18
- Swipe your bottom screen to show the navigation bar
- The navigation bar will keep staying on screen.
Version/Commit
In my case, this issue occurs in v1.18.0, v1.19.0, v1.19.1 and v1.20.0
Bisect Results
From skimming the code, my guess it broke on 5452999
Present in the nightly version
Yes, this is reproduced in the nightly build
Platform & operating system
Android v10
Affected Cores
No response
Environment information
No response
Relevant log output
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 navigation-bar behavior on Android 10 using RetroArch 1.18 or newer, then compare it with the expected behavior shown for version 1.17.0. Review commit 5452999 as the reported bisect point; the fix is complete when swiping up to show the navigation bar no longer leaves it permanently visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, c
- Domain
- frontend, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100