[release/11.0-rc1] Fix auto-pause when circuit starts after enhanced navigation - #68612
Merged
akoeplinger merged 1 commit intoAug 18, 2026
Merged
Conversation
* fix auto-pause issue * resolve streaming rendering case --------- Co-authored-by: Ilona Tomkowicz <itomkowicz@microsoft.com>
kotlarmilos
approved these changes
Aug 18, 2026
ilonatommy
added
area-blazor
This was referenced Aug 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #68540 to release/11.0-rc1
/cc @ilonatommy @surya3655
Fix auto-pause when circuit starts after enhanced navigation
Description
Auto-pause that is a deployment resources saving mechanism for interactive server apps was working only when client's page was loaded via full page load. If it was loaded with enhanced navigation from SSR static rendering, the mechanism wouldn't trigger. The auto-pause feature was introduced in net11.
The issue was caused by wrong timing of reading configuration at the wrong time when going interactive. The PR discovers server-emitted browser configuration from the initial document or enhanced-navigation response, merges it into the client/circuit options, and applies it before the interactive circuit starts for both: SSR static rendering and SSR static streaming rendering.
Fixes #68337
Customer Impact
Affected types of apps: interactive server with prerendering.
Regression?
Auto pause feature was not present in net10.
Risk
It changes browser-configuration processing for every Blazor streaming update and the timing for consuming circuit options (on lazy server startup instead of during initial Blazor Web boot).
Verification
Packaging changes reviewed?