Skip to content

Support persistent component state across enhanced page navigations #51584

Description

  • Right now persistent component state only works during the initial render of the components for a given runtime.
  • This is because it doesn't know about enhanced navigations and because we don't have a mechanism to deliver state updates to components that are already running.

This issue tracks adding a new mechanism to deliver state updates from enhanced navigations coming from the server to running runtimes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

Pillar: Complete Blazor WebPriority:1Work that is critical for the release, but we could probably ship withoutarea-blazorIncludes: Blazor, Razor ComponentsenhancementThis issue represents an ask for new feature or an enhancement to an existing onetriaged

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions