<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary <!-- Summarize the bug encountered concisely. --> When: 1. Looking at a specific commit in an MR which has a different amount of changes than the MR itself, and 2. Scrolling down and having the tabs follow The number of changes jumps between the number of changes in the MR to the number of changes in the commit when switching between the "scrolling mode" of the tab bar and the regular display. ### Steps to reproduce 1. Look at an MR with some changes (e.g. https://gitlab.com/gitlab-org/gitlab/-/merge_requests/164348/diffs). 2. Choose a specific commit from the commits page and look at the diff (e.g. https://gitlab.com/gitlab-org/gitlab/-/merge_requests/164348/diffs?commit_id=095a7402e0fb005a417cfe1e2b94e5ba95fe9476) 3. Scroll down and look at the number of changes <!-- Describe how one can reproduce the issue - this is very important. Please use an ordered list. --> ### Example Project <!-- If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version. --> ### What is the current *bug* behavior? <!-- Describe what actually happens. --> The number of changes jumps between the number of changes in the MR to the number of changes in the commit when switching between the "scrolling mode" of the tab bar and the regular display. ### What is the expected *correct* behavior? The number of changes should stay the same and reflect the number of changes in the current context (i.e. the commit I'm looking at) regardless of my position on the page. <!-- Describe what you should see instead. --> ### Relevant logs and/or screenshots A video!  <!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise. --> ### Output of checks <!-- If you are reporting a bug on GitLab.com, uncomment below --> <!-- This bug happens on GitLab.com --> <!-- /label ~"reproduced on GitLab.com" --> #### Results of GitLab environment info <!-- Input any relevant GitLab environment information if needed. --> <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`) </pre> </details> #### Results of GitLab application Check <!-- Input any relevant GitLab application check information if needed. --> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`) (we will only investigate if the tests are passing) </pre> </details> ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->