You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi team, I’d like to suggest a small rewrite to improve clarity in the following paragraph from the Blazor Server prerendering documentation:
While technically accurate, this paragraph uses uncommon terminology (e.g., “quiescence”) without immediate clarification. For readers unfamiliar with Blazor’s internals, it may be hard to grasp the practical implications.
I’d like to propose a more accessible version:
"In Blazor Server apps, prerendering waits until all components in the render tree have finished rendering before displaying any content. This behavior, known as quiescence, means that if a component performs long-running tasks during initialization, it can delay the entire page from appearing—leading to a poor user experience."
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi team, I’d like to suggest a small rewrite to improve clarity in the following paragraph from the Blazor Server prerendering documentation:

While technically accurate, this paragraph uses uncommon terminology (e.g., “quiescence”) without immediate clarification. For readers unfamiliar with Blazor’s internals, it may be hard to grasp the practical implications.
I’d like to propose a more accessible version:
I believe this version improves readability while preserving the technical meaning. Let me know what you think!
https://learn.microsoft.com/en-us/aspnet/core/blazor/components/lifecycle?view=aspnetcore-10.0#quiescence-during-prerendering
Beta Was this translation helpful? Give feedback.
All reactions