fix: browser back navigation fails with hash URLs#17081
Merged
Conversation
Hash links were rendered as plain <a> tags, which meant browser history was managed natively. When navigating from a subpage back to a page with a hash URL (e.g., /community/events#conferences), the browser interpreted this as a same-page scroll rather than a route change, causing the UI to stay on the wrong page. Switching hash links to use I18nLink ensures the Next.js router properly manages history, so back navigation triggers a full route change. Fixes ethereum#17080
minimalsm
requested review from
corwintines,
pettinarip and
wackerow
as code owners
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
wackerow
approved these changes
Jan 15, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes browser back button navigation failing when returning to a page with a hash URL fragment. The issue occurred because hash links were rendered as plain
<a>tags, causing the browser to interpret back navigation as a same-page scroll rather than a proper route change.BaseLinkcomponent to useI18nLink(Next.js router) instead of native<a>tagsFixes #17080
Test plan
/community/events/community/events/meetups//community/eventsand displays the main events page content