Update 04-linking-and-navigating.mdx, Partial Rendering, explain about unmounting and losing state #70397
+1
−1
Conversation
This file contains 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
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
|
I think it's more correct to say that the components will be unmounted and remounted, and thus lose state. |
ijjk
reviewed
Sep 24, 2024
| @@ -263,7 +263,7 @@ Learn more about how the [Router Cache](/docs/app/building-your-application/cach | |||
|
|
|||
| Partial rendering means only the route segments that change on navigation re-render on the client, and any shared segments are preserved. | |||
|
|
|||
| For example, when navigating between two sibling routes, `/dashboard/settings` and `/dashboard/analytics`, the `settings` and `analytics` pages will be rendered, and the shared `dashboard` layout will be preserved. | |||
| For example, when navigating between two sibling routes, `/dashboard/settings` and `/dashboard/analytics`, the `settings` and `analytics` pages will be fully rendered (pages will unmount and state will be lost), and the shared `dashboard` layout will be preserved. | |||
There was a problem hiding this comment.
Suggested change
| For example, when navigating between two sibling routes, `/dashboard/settings` and `/dashboard/analytics`, the `settings` and `analytics` pages will be fully rendered (pages will unmount and state will be lost), and the shared `dashboard` layout will be preserved. | |
| For example, when navigating between two sibling routes, `/dashboard/settings` and `/dashboard/analytics`, the `settings` page will be unmounted, the `analytics` page will be mounted with fresh state, and the shared `dashboard` layout will be preserved. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What?
Update 04-linking-and-navigating.mdx, 4. Partial Rendering section, add information that rerenders of sibling routes mean full rerender of the page, unmounting and losing the state of the page
Why?
I've spent a lot of time trying to understand why in the app router when switching between sibling routes (and Dynamic Segments) I lose scroll position. Finally, find a discussion that this is the intentional behaviour of the Next.js team. Would be good if the Next.js users could find information in the documentation instead of searching for issues and discussions in the documentation.
#50711
How?
Updated docs