InteractiveAuto behavior needs more details regarding when it's using WebAssembly.

Description

The article says:

The .NET runtime and app bundle are downloaded to the client in the background and cached so that they can be used on future visits.

Which I interpret as once the client is fully downloaded the Auto will use WebAssembly from there on.

Examples

• Reloading an Auto page will run it as WebAssembly as expected
• Navigating back and forth between an Auto and WebAssembly page will render the Auto page in WebAssembly
• Navigating to an (Interactive)Server page and then to an Auto page will not launch the WebAssembly but instead run the Auto page as (Interactive)Server.

Thus "future visits" need to be clarified that it depends on how the visitor navigates and not only whether the runtime and app is fully downloaded.

Page URL

https://learn.microsoft.com/en-us/aspnet/core/blazor/components/render-modes?view=aspnetcore-8.0#automatic-auto-rendering

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/render-modes.md

Document ID

7c9948a3-9886-8097-6014-492a4c21ea4e

Article author

@guardrex

[github-actions]

🍂🎁 Happy Holidays! ❄️⛄

A green dinosaur 🦖 will be along shortly to assist. Stand-by ........

[guardrex]

Thanks @breakerofbuilds ... I agree; but in the third case, I would guess the Auto page runs initially with WASM because the WASM runtime is active.

@MackinnonBuck ... Can you clarify what "on future visits" means? I'll add remarks to the article.

[guardrex]

There's one thing that we'll probably need to add (I'll look on Monday to see how we're handling it) ... Auto components are still prerendered on the server. Therefore, we'll need to make sure that it's clear that even if the Blazor runtime is active on the client, there's a prerendering step on the server. Then, we need to flesh out if page transitions affect CSR. I don't think so ... I think after the Blazor client becomes active (and after prerendering) that Auto components always render on the client. However, I assumed that was the case from product unit remarks and didn't inquire further.