Function "Jump to line" doesn't work

[ngoclong19]

Select Topic Area

Bug

GitHub Feature Area

UI/UX

Body

This was originally reported at: https://support.github.com/ticket/3176669
GitHub Support told me to submit it here since their engineers couldn't reproduce the error.

Actual Result

The function "Jump to line" doesn't work with the "Go" button. It only works with the Enter key.

Expected Result

The function works with both the Enter key and the "Go" button.

Environment

Windows 10 Pro 22H2 19045.5247 (64-bit)
Mozilla Firefox 133.0.3 (64-bit)
Microsoft Edge 131.0.2903.146 (64-bit)
No browser add-on.
The bug happens with or without signing in.

Reproduction Steps

1. Visit https://github.com/dracula/hacker-news/blob/main/dracula.user.css
2. Press the l key to open the "Jump to line" dialog
3. Input 5, click the "Go" button
4. The cursor jumps to line 1. In the browser address bar, the URL ends with the anchor #L1.
5. Press the l key to open the "Jump to line" dialog
6. Input 10, click the "Go" button
7. The cursor stays at line 1. In the browser address bar, the URL ends with the anchor #L1.
8. Press the back navigate button of the browser (shortcut key Alt+Left). In the browser address bar, the URL is clear of anchors.
9. Press the l key to open the "Jump to line" dialog
10. Input 5, press the Enter key
11. The cursor jumps to line 5. In the browser address bar, the URL ends with the anchor #L5.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[cehfisher]

Hello @ngoclong19 - thank you for taking the time to provide this feedback! The GitHub accessibility team reviewed this issue and were able to reproduce it and are now actively working on this issue. We will follow-up here with any additional questions or updates. Thanks again!

[cehfisher]

Hello @ngoclong19 - great news, this issue has been resolved! Could you please re-test this on your machine to be sure the update resolved your issue?

[ngoclong19]

@cehfisher: Thank you for your feedback! I confirm that the issue is fixed partially.

If, for example, I jump to line 15 with the Go button, the cursor will go to line 15, but the URL has some random anchor, like https://github.com/dracula/hacker-news/blob/main/dracula.user.css#L1. The URL briefly has the anchor #L15 then it switched to some random number.

Using the Enter key instead, the cursor will move to the specified line number (line 15), and the URL has the expected anchor (#15).

The cursor position and URL anchor behaviors are described in my original report above.

[cehfisher]

Thanks for the additional details @ngoclong19 - we will pass along this information to the team to look into this issue a bit deeper.

[Aditya1286]

This is a clear bug report about GitHub's "Jump to line" feature not working correctly with the "Go" button. Let me break down what's happening:

Issue Summary: The "Jump to line" feature in GitHub's code view works when using the Enter key but fails when clicking the "Go" button.

Reproduction Pattern:

When you input a line number and press Enter, it correctly jumps to that line and updates the URL with the proper anchor (like #L5)

When you input a line number and click the "Go" button:

First attempt: Jumps to line 1 (incorrect behavior)

Subsequent attempts: Stays at line 1 and doesn't navigate to the requested line

Environment Details:

Windows 10 Pro with latest updates

Reproduced on both Firefox and Edge browsers

Happens regardless of login status

No browser extensions involved

This appears to be a legitimate UI/UX bug in GitHub's code navigation interface. Since GitHub Support couldn't reproduce it but acknowledged your report by directing you to the community discussions, it might be an intermittent issue or dependent on specific environment conditions.

Have you been able to reproduce this on other repositories or is it specific to the dracula/hacker-news repository? Also, have you tried this on any other operating systems or browsers?

[cehfisher]

Thanks for joining the conversation @Aditya1286! We've shared these details with the team and will provide updates as soon as we have them.

[cehfisher]

Hello @ngoclong19 and @Aditya1286 - there have been some recent updates that hopefully have resolved your issue. Could you please clear your browser cache and retest? Thanks!

[ngoclong19]

Thank you! I confirm that this issue is fixed.

[yuriev-yuriy]

Maybe it’s worth exploring a debounce or delay to let the anchor settle before switching? Curious what others think 🤔

[cehfisher]

Thank you for your additional feedback @yuriev-yuriy! We appreciate your input and will add your suggestion to our internal tracking issue.

Since the original issue has been resolved, this thread will be closed soon. That said, feel free to start a new post if you’d like to continue the discussion of further improvements to this feature with the community.