How does Blazor Server's reliance on a persistent SignalR connection affect its behavior under network interruptions?

Since all UI state and event handling logic actually executes on the server, a Blazor Server app's interactivity entirely depends on its SignalR connection -- if the connection drops (network blip, server restart, idle timeout), the UI becomes unresponsive until reconnection succeeds, at which point Blazor attempts to resync client-side DOM state with the server, though any unsaved in-progress state can be lost if reconnection fails entirely, showing a default 'Attempting to reconnect' overlay.

// Customizing reconnection UI behavior in Blazor Server
<div id="components-reconnect-modal">
    Connection lost. Attempting to reconnect...
</div>

// Configuring reconnection retry intervals
builder.Services.Configure<CircuitOptions>(options => {
    options.DisconnectedCircuitMaxRetained = 100;
});