dotnet/aspnetcore

Follow links when disconnecting

Open

#9,964 opened on May 4, 2019

View on GitHub
 (9 comments) (0 reactions) (0 assignees)C# (37,933 stars) (10,653 forks)batch import
affected-mediumarea-blazorenhancementfeature-blazor-servergood first issuehelp wantedseverity-major

Description

As soon as you have lost contact with blazor.server.js, any transition to the links of the prejudice causes the error 'blazor.server.js:1 Uncaught (in promise) Error: Cannot send data if the connection is not in the 'Connected' State.'

I suggest in the absence of communication with the server to perform the usual transition by reference, without using server rendering. In this case, you do not need to display a window about disconnect, and the normal reconnection will be performed with the page reloading.

Contributor guide

Tech stack
csharpjavascript
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic understanding of Blazor ServerJavaScript basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate the Blazor Server navigation handling in the repository, particularly in files related to the connection state and link navigation (e.g., within the Components/Server directory). Review the linked GitHub issue #9964 for the proposed solution. Consider how to intercept link clicks and fallback to regular navigation when the connection is lost, ensuring reconnection occurs on page reload.