[Feature Request] [Ozone] Breadcrumbs for easier menu navigation
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Taken from point 4 in this thread: https://github.com/libretro/RetroArch/issues/14143
The Ozone UI is in dire need of breadcrumbs, ie an indication in the UI of the user's position in the menu at any given time.
The header bar in the Ozone UI should display the entire "path" reached by the user at any given time in the menu, to facilitate the user's navigation as well as provide a more reliable visual reference for troubleshooting, etc.
Here's a few examples of how it would look:
"Settings > Video > Output" (when selecting any normal Menu entry / option)
"Name of the Playlist" > "Name of the playlist entry" (when selecting any playlist entry)
The ">" separator was chosen here because of a similar implementation that already exists in RA, when performing a search in any playlist:

To accommodate those scenarios where the length of the path shown in the header may exceed the width of the UI:
- either the text could be made to shrink dynamically down to a minimum amount (preferrable approach, as far as I am concerned);
- or some form of horizontal scrolling could be used - such as what happens with playlist metadata when enabling Settings -> User Interface -> Appearance -> Ticker Text Animation.
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 locating the Ozone UI code that renders the header bar and menu navigation, then compare it with the existing playlist search path display and ticker text behavior described in the issue. Done means the header shows the complete current menu or playlist path, with a defined behavior when the path exceeds the available width.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100