Auto switching for interactive components #46397
Assignees
Labels
area-blazor
Includes: Blazor, Razor Components
enhancement
This issue represents an ask for new feature or an enhancement to an existing one
feature-full-stack-web-ui
Full stack web UI with Blazor
Priority:1
Work that is critical for the release, but we could probably ship without
Milestone
Comments
mkArtakMSFT
added
enhancement
|
Does auto mode support automatic switch besides re-ender switch? |
This was referenced Jul 18, 2023
mkArtakMSFT
pushed a commit
that referenced
this issue
Jul 21, 2023
…de dynamically (#49578) # Support for determining the render mode dynamically Adds basic support for using the "Auto" render mode in Blazor apps. This allows the render mode for a component to resolve to either "Server" or "WebAssembly" depending on whether the WebAssembly runtime is downloaded and available on the client. Backport of #49477 ## Description In full-stack Blazor apps, components can be made interactive either via "WebAssembly" or "Server" render modes. The WebAssembly render mode has the advantage that it consumes fewer server resources, but the disadvantage that it delays "time to interactivity" because .NET WebAssembly runtime resources must be downloaded to the client first. Therefore, the "auto" render mode was introduced so that it: * Uses the WebAssembly render mode if the client already has the WebAssembly bits cached * Uses the Server render mode in other cases, while downloading WebAssembly resources in the background We also intend to add support for customizing the policy that determines which render mode "auto" mode should resolve to, but that's not included as part of this PR. Before this change, attempting to use the "auto" render mode would result in an error in the browser console and an unusable app. This PR allows customers to start experimenting with auto mode for their apps. Fixes #46397 ## Customer Impact Medium. The Auto render mode is already one of the three render modes customers can pick, but currently it just breaks the app. As we get closer to GA, we expect lots of customers to start trying out auto mode, so we'd like this feature to be made available as soon as possible so we can collect feedback and make the necessary corrections. ## Regression? - [ ] Yes - [X] No ## Risk - [ ] High - [ ] Medium - [X] Low This feature shouldn't impact functionality for existing Blazor Server/WebAssembly apps. It won't introduce a regression in the existing auto mode implementation, because the current implementation throws an exception. ## Verification - [X] Manual (required) - [ ] Automated
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In scope:
Out of scope:
The text was updated successfully, but these errors were encountered: