<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=398176) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal My suggestion is to enhance the static breadcrumb that is displayed while navigating a project's files. Specifically, I'd like to see dynamic navigation similar to how the breadcrumbs within Visual Studio Code operate. Let's imagine the following very simple project structure. ``` - src | - components | - Header | - index.js - Header.js - helpers.js - Body - Footer - utils - package.json ```  If I am currently viewing Header.js, I'd like to be able to click (possibly a new dropdown) a crumb and see the other files/directories at that level and be able to navigate into them directly. It would save time having to navigate back a bunch and down into directories and reduce the constant opening of things in new browser tabs. Here is a screenshot of how Visual Studio Code would show this scenario. <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->