Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect section #15270

Closed
javiercn opened this issue Oct 23, 2019 — with docs.microsoft.com · 0 comments · Fixed by #15272
Closed

Incorrect section #15270

javiercn opened this issue Oct 23, 2019 — with docs.microsoft.com · 0 comments · Fixed by #15272
Assignees
Labels

Comments

Copy link
Member

> The client reconnects to the server with the same state that was used to prerender the app. If the app's state is still in memory, the component state isn't rerendered after the SignalR connection is established.

This paragraph is obsolete. We don't do "stateful" prerendering anymore, we connect from the client to the server and produce another render after prerendering.

Could we get this fixed?

dotnet/aspnetcore#15266


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@dotnet-bot dotnet-bot added ⌚ Not Triaged Blazor Source - Docs.ms Docs Customer feedback via GitHub Issue labels Oct 23, 2019
@guardrex guardrex self-assigned this Oct 23, 2019
@guardrex guardrex added doc-bug Pri0 Urgent priority and removed ⌚ Not Triaged Source - Docs.ms Docs Customer feedback via GitHub Issue labels Oct 23, 2019
@guardrex guardrex added this to the 2019 Q4 ends Dec 31 milestone Oct 23, 2019
@Rick-Anderson Rick-Anderson moved this to Done in Blazor.Docs Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants