Change behaviour for custom protocol links in blazor apps

[MarvinKlein1508]

Is your feature request related to a problem? Please describe.

I want to link a custom protocol to a hyperlink. Whenever the user clicks on it, the SignalR connection will be closed and established again automatically. A workaround for this is to set target="_blank" for the hyperlink but this leaves the user with an open blank tab.

Describe the solution you'd like

It already works fine for the mailto: protocol, so why do other protocols behave differently? However, the mailto: protocol results in the same if you call it with navigationManager.NavigateTo()

Sometimes it is necessary to load data first which you want to forward with the protocol. So I think the NavigateTo() should be able to do the same thing just without closing the SignalR connection.

Additional context

I created a small repo to show exactly what I mean

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[mkArtakMSFT]

@captainsafia isn't this fixed already?

[captainsafia]

Yes, this was already fixed. We have tests to cover the mailto protocol scenario. It looks like this issue is related to a different custom protocol so that might have something to do with it.

• Can you try setting the forceReload property in your NavigateTo call?
• What is the custom protocol you are trying to use? Do you repro the same issue with mailto?

[MarvinKlein1508]

@captainsafia

I tested it yesterday with the latest public .NET 6 and it still has the same behaviour as mentioned above.

We created our own protocol which should open an installed C# console application with a parameter and do a simple task which is not possible otherwise.

Also we need to call the mailto within the navigation manager because there are multiple possible email addresses in our case which we need to get first from the database before we can navigate with mailto (as well as some attachments needs to be created first).

Sire I can try to set force reload to true but we don‘t want the page to reload while calling a custom protocol.

[captainsafia]

So we validate the mailto link scenario in our own tests here:

aspnetcore/src/Components/test/E2ETest/ServerExecutionTests/CircuitGracefulTerminationTests.cs

Line 95 in 8b30d86

public async Task NavigatingToProtocolLink_DoesNotGracefullyDisconnect_TheCurrentCircuit()

Are you able to provide a repro for this? Otherwise it's hard how to see our validations pass for custom protocols (or at least mailto links).

[MarvinKlein1508]

@captainsafia I updated my example repro from above for you. You can find it here:
https://github.com/MarvinKlein1508/ProtocolExample

I put six scenarios for you in it.
1.) mailto as href
2.) mailto with navigationManager
3.) mailto with new tab
4.) Custom protocol with href
5.) Custom protocol with navigationManager
6.) Custom protocol with new tab

To test the custom protocol you'll need to register it within your registry first.

[MarvinKlein1508]

@captainsafia did you find some time to check the repro out?

[captainsafia]

@MarvinKlein1508 Yes -- admittedly, I had trouble setting the custom protocol registration up so I ended up replacing myprotocoll with a protocol that was already registered on my machine (notion).

For that scenario, I wasn't able to reproduce the SignalR connection closing. Is there any chance it might be an issue with the protocol you registered?