Blazor 8 PersistentComponentState and Enhanced Navigation

[oliverw]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I have noticed that when navigating inside a Blazor 8 Web App, components using @rendermode InteractiveAuto are rendered once on the server during pre-rendering at which point I store the state in PersistentComponentState. When the component is rendered the second time on the client, the state is not available forcing the client to load the data a second time using a http request. Is this working as intended? Sounds like a waste of computation resources.

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

8.0.100-rc.2.23502.2

Anything else?

No response

[MackinnonBuck]

Thanks for filing the issue, @oliverw!

The current mechanism for persistent component state only allows reading persisted state after the initial page load. This currently excludes enhanced navigations, but we have #51584 to track having better support for the enhanced navigation scenario.

I'm going to close this out as a duplicate of the existing issue. Thanks again 🙂

[Markz878]

@MackinnonBuck @danroth27: Really worrying that people who are stuck on LTS releases will have to deal with this performance issue for 2 years if this is not fixed.