Open scrabase opened 4 months ago
This happens only when the server action does a revalidation (path or tag), and the action returns the updated page. This causes the navigated page to wrongfully replace its real content with the action result. It's weird, because the URL will show the new URL, but the page will be the previous page.
Link to the code that reproduces this issue
https://github.com/scrabase/bug-next-server-actions-block-navigation
To Reproduce
Current vs. Expected behavior
current: navigation blocked when server action running expected: navigation should not blocked when server action long running
Provide environment information
Which area(s) are affected? (Select all that apply)
create-next-app, Navigation
Which stage(s) are affected? (Select all that apply)
next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)
Additional context
https://github.com/vercel/next.js/issues/49425 resolved this issue. But in next@14.2.3 this bug this bug occurred again. I have checked that canary versions also have this bug.
I just copied https://github.com/Fredkiss3/bug-next-server-actions-blocking-navigation this repo and did just chagned to latest next version and bug occured
in summary: next@13.4.20-canary.1 -> no bug next@14.2.3 -> bug