### Problem to solve When doing code review you sometimes want to follow a newly initialized and declared variable. This is hard to do since you need to ctrl+f the variable. ### Intended users Development Team Lead Software Developer DevOps Engineer ### Further details The use case is the code review. A benefit is the improvement of code review in terms of quality and speed (Faster understanding of context) <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> ### Proposal As a developer, when I select a variable, the same variable should be highlighted elsewhere in the diff. This would be the same as the Web IDE. ### Permissions and Security You need to be able to view the merge request diff ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further guidelines: https://about.gitlab.com/handbook/engineering/quality/guidelines/test-engineering/ --> ### What does success look like, and how can we measure that? A success of this proposal would improve the merge request review. A measurement could be the number of times the code highlight feature is used. ### Links / references