[Blazor] Script in HeadContent vs. enhanced navigation #34518
Merged
Conversation
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
Collaborator
|
Thanks, @hakenr ... This came from Sanderson earlier this week, and he didn't mention the additional qualifier in discussion. Let's get past the MLK holiday weekend, and I'll message him to take a look next week. The qualifier that's changing for the "removes the - a Blazor Web App using an interactive render mode (interactive SSR, CSR)
+ a Blazor Web App using either an interactive render mode (interactive SSR, CSR) or static SSR with enhanced navigation |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
I think this isn’t about interactive vs. static rendering, but rather depends on whether the page instance is preserved in browser. If the DOM is being patched (interactive or static with enhanced navigation), the instance is retained. However, if a new page instance is created (static SSR without enhanced navigation), it behaves differently.
Internal previews