<!--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=323770) </details> <!--IssueSummary end--> ### Problem to solve It's not currently possible to select multiple lines within a snippet to highlight and anchor against. When Shift-Clicking the secondary line a new window is opened instead. ### Intended users * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Rachel (Release Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#rachel-release-manager) ### User experience goal - Ability to reference a range of code within a file. - Consistent experience across the gitlab product #### Example from `gitlab-org/gitlab` multi-line highlighting  ### Proposal Bind Shift-Click to selecting a line range rather than opening a new window ### Documentation TODO: Do we document these kind of interactions? ### Availability & Testing TODO <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? 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? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> ### Available Tier ~"GitLab Core" ### What does success look like, and how can we measure that? See UX goal ### What is the type of buyer? ~"GitLab Core" ### Links / references