Bug: Page scroll position not preserved after route navigation

[jamunatg2006-sys]

Description

When navigating between pages/routes within the application, the scroll position is not handled consistently. Users may return to the top unexpectedly or lose their previous reading position after navigating back.

Steps to Reproduce
Open a page with enough content to scroll.
Scroll down to a lower section.
Navigate to another internal route/page.
Use back navigation or return to the previous page.
Observe the scroll behavior.
Expected Behavior
Previous scroll position should be restored when navigating back.
OR
App should consistently reset to top (depending on intended behavior).
Actual Behavior

Scroll position resets inconsistently / previous position is lost, affecting navigation experience.

Impact
Poor UX for users reading long content pages
Extra scrolling required after navigation
Inconsistent route behavior
Possible Cause

Missing scroll restoration handling in router/navigation lifecycle.

Suggested Fix

Implement scroll restoration logic:

Save scroll position before route change
Restore on back navigation
Ensure consistent top-scroll on fresh route loads

[github-actions]

👋 Thanks for opening an issue, @jamunatg2006-sys!

Our maintainers will review this shortly 🚀

Before you start working

• 📖 Read the CONTRIBUTING.md guide
• 💬 Wait for a maintainer to assign you the issue before starting work
• 🔍 Search for existing issues to avoid duplicates

For GSSoC'26 contributors

If you're contributing under GirlScript Summer of Code 2026, please mention it in your comment when requesting assignment:

"I'd like to work on this — contributing under GSSoC'26"

Architecture notes

Reframe is a static Next.js app with output: "export". Key points:

• All video processing uses FFmpeg.wasm (client-side, no server)
• headers() in next.config.ts won't work — use vercel.json instead
• not-found.tsx requires public/404.html + vercel.json routes config

Happy contributing! ⭐ Star the repo if you find it useful!

[vishesh1111]

Hi! I'm @vishesh1111 , a GSSoC'26 contributor and I'd love to work on this issue.
I've gone through the repo structure and the CONTRIBUTING.md guide. My approach would be:

Save scroll position before route change using Next.js router events
1.Restore it on back navigation
2.Reset to top on fresh route loads

Could a maintainer please assign this issue to me? I'd like to work on this — contributing under GSSoC'26.

[Prashant-kumar-8312]

/assign

[github-actions]

Hey @Prashant-kumar-8312, this issue has been assigned to you! 🎉 Please make progress within 5 days or it will be automatically unassigned due to inactivity.

[jamunatg2006-sys]

Hi, I had spent quite a bit of time analyzing and reproducing this issue before raising it, and I’ve already started working on a fix (currently halfway done). If possible, I’d really appreciate being assigned to this issue so I can complete and contribute the solution. Thank you!

[Prashant-kumar-8312]

/unassign

[github-actions]

Hey @Prashant-kumar-8312, you have been unassigned from this issue. It is now open for anyone to pick up — comment /assign to claim it! 👋

[aaniya22]

pls assign this to me under gssoc'26

[aaniya22]

/assign

[github-actions]

Hey @aaniya22, this issue has been assigned to you! 🎉 Please make progress within 5 days or it will be automatically unassigned due to inactivity.