2 people reported
All time, since Sep 29.
router.refresh() triggers full document reload with parallel route modals
“Any client state on the background page and in the modal is lost.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/next-js/issues/4124/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
router.refresh() triggers full document reload with parallel route modals. Refreshing from an intercepted or parallel-route dialog replaces the browser document, losing the background page and client state.
Is this your bug?
File my report- Where
- App Router
- Versions
- 16.4.0-canary.51 to 16.4.0-canary.59
- Platforms
- macOS, Windows
- How bad
- Breaks a normal workflow.
Not quite your bug?
Original reports2, newest first
- Refresh under an intercepted modal falls back to an MPA navigation when the background page is itself interceptable (Next-Url sent on the reused route's refresh request)On GitHub#99658
- App Router: router.refresh() causes a full-page reload with retained parallel routes inside a route groupOn GitHub#99444