Add remarks on prerendering with interactive routing

[guardrex]

Description

Per offline discussion with Mackinnon ... internal navigations are interactive with an interactive router and don't involve requesting new page content from the server. Therefore, prerendering doesn't occur.

Also ...

The current persistent component state feature only works on the initial page load. That is, if you perform a full (non-enhanced) navigation to a page utilizing persistent component state, the persisted state will be made available for the app to use when it becomes interactive, and things will work as expected. But if an interactive circuit has already been established and an enhanced navigation gets performed to a page that renders persisted component state, that state will not be made available in the existing circuit.

Goals ...

• Add remarks on both behaviors.
• Add remarks to prerendering examples that if using an interactive router to use a full page reload to see the demo behavior explained by the article.

Page URL

https://learn.microsoft.com/en-us/aspnet/core/blazor/components/prerender?view=aspnetcore-8.0

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/prerender.md

Document ID

ffdc8df3-55a8-b757-d4e6-38c104916002

Article author

@guardrex