Issue Summary:
When browsing the repository search results on GitHub, navigating into a repository and then clicking the "Back" button (or returning to the search page) resets the scroll position to the top of the page. This forces the user to scroll down manually to find their previous position, which significantly disrupts the browsing workflow.
Steps to Reproduce:
Go to the GitHub search page (e.g., searching for "OpenSearch" or any other topic).
Scroll down to a specific repository result.
Click on that repository to view its contents.
Click the "Back" button in the browser to return to the search results page.
Expected Behavior:
The browser should return to the exact scroll position where the user was before they navigated into the repository.
Actual Behavior:
The page reloads or returns to the top of the search results, causing the user to lose their current position.
Impact:
This negatively affects the user experience, especially when evaluating multiple repositories in a single search session, as it increases unnecessary scrolling and navigation time.
Suggestion:
It would be a great quality-of-life improvement if GitHub could implement state preservation or use history API techniques to maintain the scroll position upon returning to the search results page.
Thank you.
Issue Summary:
When browsing the repository search results on GitHub, navigating into a repository and then clicking the "Back" button (or returning to the search page) resets the scroll position to the top of the page. This forces the user to scroll down manually to find their previous position, which significantly disrupts the browsing workflow.
Steps to Reproduce:
Go to the GitHub search page (e.g., searching for "OpenSearch" or any other topic).
Scroll down to a specific repository result.
Click on that repository to view its contents.
Click the "Back" button in the browser to return to the search results page.
Expected Behavior:
The browser should return to the exact scroll position where the user was before they navigated into the repository.
Actual Behavior:
The page reloads or returns to the top of the search results, causing the user to lose their current position.
Impact:
This negatively affects the user experience, especially when evaluating multiple repositories in a single search session, as it increases unnecessary scrolling and navigation time.
Suggestion:
It would be a great quality-of-life improvement if GitHub could implement state preservation or use history API techniques to maintain the scroll position upon returning to the search results page.
Thank you.