fix: now the page scrolls to top position when navigated to previous … #184
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.
…page
Description
The problem was in the scroll position retention during client-side routing. When navigating between pages, the scroll position of the previous page was preserved instead of resetting to the top of the new page. This caused confusion and a poor user experience.
The issue was resolved by using the
usePathname()hook from Next.js to detect route changes and calling window.scrollTo(0, 0) inside a useEffect, which resets the scroll position whenever the route changes.Fixes #55
Type of change
Please delete options that are not relevant.
Checklist: