<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal This is a simple browser-side UI proposal which results in less hassle while navigating large merge requests. When viewing diffs in merge request with multiple files, there are `< Prev | Next >` buttons below the diff (if we are viewing single file at a time). Because diffs have different height, these navigation buttons jump up and down and you have to find them every time you switch the file. Currently i use custom CSS which fixes them in one place and makes a bit transparent.  <!-- 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. --> CSS is very simple and i had no issues with it so far: ```css [data-testid="file-by-file-navigation"] { position: fixed; bottom:0%; left: 50%; background-color: #ffffff66; } ``` It would be nice to have this as an option somewhere! <!-- 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. -->