InteractiveAuto is not working

[wendellestradairely]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

According the to Blazor [documentation]((https://learn.microsoft.com/en-us/aspnet/core/blazor/fundamentals/?view=aspnetcore-10.0), if the render mode of a page/component is configured as InteractiveAuto, "Interactive SSR using Blazor Server initially and then CSR on subsequent visits after the Blazor bundle is downloaded"

However, the component is not interactive until all the wasm/dll files are downloaded.

Expected Behavior

Since, the component/page is configured as InteractiveAuto, it should be interactive initially via SignalR even the wasms are still being downloaded.

Steps To Reproduce

1. Create a new Blazor web app. dotnet new blazor -int Auto -ai
2. Run the app.
3. Navigate to the Counter page.
4. Hit refresh.
5. While the wasms are still being downloaded, click the Counter button.

Exceptions (if any)

No response

.NET Version

.NET 10 rc1

Anything else?

No response

[MihuBot]

I'm a bot. Here are possible related and/or duplicate issues (I may be wrong):

• InteractiveAutoRenderMode(prerender:false)) does not use interactive server rendering #54657
• Setting rendermode to InteractiveAuto does not use Interactive Server rendering #63596
• [Blazor] Auto Render not working properly in .NET 8 and page locks until WebAssembly start #52154

[javiercn]

@wendellestradairely thanks for contacting us.

InteractiveAuto uses a timeout before it starts the app in InteractiveServer render mode. It only uses Server render mode if webassembly doesn't load fast enough.

Note that it won't load webassembly until the next full-page refresh once server has started.

[dotnet-policy-service]

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.