[BUG] entering the Debug Mode in WebAssembly served on Server (startup Proj) messes up Navigation

[DevTKSS]

Description

Entering Debug mode using Shift+Alt+D on Login Page sets the BrowserTab Name to Main + opens the Debug Address on MainPage instead of LoginPage

Changing back to the non debug tab, will still show Login screen but the changed Tab Name of Main.

• Startup project Server
• application url in props has been added by https of 5001
• server urls has been changed in order so the https is the first one
• Server base setup guide has been followed for https allowance of "insecure contents"

🤔 inspecting Blazor Host setup, they are Mapping the framework debug path in:

if (app.Environment.IsDevelopment())
{
    app.UseWebAssemblyDebugging(); //<-- look Decompilation

do not see anything like this in the included Uno Package that would do the same.
Does it miss on this?

Steps to Reproduce

• Use this result of the before described issue: UnoApp5 (2).zip
• Make sure you select Server as Startup Project and you did set https://localhost:5002 to allow unsafe contents
• start in Debug using F5 (Browser Chrome)
• If you did not set the unsafe contents setting for this url so far, you will get a Error Pop up, thats caused by Mixed Contents and no Cors setup, DO NOT CLICK ANY BUTTON OF IT! otherwhise the debug session will just end.
• opening developer tools in Chrome browser
• Use Shift + Alt + D to enter your App in Debug Tab (will maybe need 2 attempts why ever)
• Tab should open fine but your route is now "Main" instead of the Login Screen where you should have been
• The non-Debug tab is still showing login, but the tab title is showing "Main"

Platform with bug

Server startup -> Wasm served on Server Project

Affected platforms

WebAssembly?

Did you find any workaround?

Not sure if it results in actual problems

Relevant log output

[DevTKSS]

Seems to be caused like here:

• Deeplinking does not work unoplatform/uno.chefs#738
  And "fixed" here:
• fix: disable url updates unoplatform/uno.chefs#1592

But Uno's "Fixed" is for this Auth requiring App up from the start page, potentially causing a critical problem, because the App does not respect that the MainPage here does require an Authenticated User.
Possibly workaround:

• DependsOn Navigation Route Parameter usage onto LoginPage?
• MainPage not above Login page in RouteMap?
• Checking src + PR?
  There seems to be no web Navigation behavior implemented, which makes it difficult
  Also, the structure in nav extensions is absolutly horrible to see the Navigation Code flow, to eventually fix it
• Not using Nav Extensions and using the NativeFrame Uri Parameters

Even if there is this fallback to "welcome page" the LoginPage is a Root Route and therefore should not cause a reset of Routes when entering Debug mode in Chrome