[.NET 5.0 RC1] NavigationManager.NavigateTo(..., forceLoad: true) stops working with empty fragment

[SommerEngineering]

Describe the bug

The bug was observed in a Blazor WASM app. If the URL ends with an empty fragment, e.g. http://localhost:5000/#, the call Nav.NavigateTo(Nav.Uri, forceLoad: true); (cf. link) does not work anymore. The code is proven to be executed, but the browser does not reload the page.

The expectation is that the browser will call the desired page in any case, because the second parameter should force a reload of the page.

To Reproduce

• git clone https://github.com/pranavkm/LocSample

• Replace the LocSample.csproj file with:

  
  <Project Sdk="Microsoft.NET.Sdk.BlazorWebAssembly">
  
  <PropertyGroup>
  <TargetFramework>net5.0</TargetFramework>
  </PropertyGroup>
  
  <ItemGroup>
  <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly" Version="5.0.0-rc.1.20451.17" />
  <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.DevServer" Version="5.0.0-rc.1.20451.17" PrivateAssets="all" />
  <PackageReference Include="System.Net.Http.Json" Version="5.0.0-rc.1.20451.14" />
  <PackageReference Include="Microsoft.Extensions.Localization" Version="5.0.0-rc.1.20451.17" />
  </ItemGroup>

**Please note:** This bug is not a .NET 5.0 RC1 regression. It's observable in .NET 3.1 LTS as well.

- Now, run `dotnet run` and open the browser at `http://localhost:5000/`.

- The culture chooser is working now.

- Now, change the url to `http://localhost:5000/#`. The culture chooser seems not to work anymore. Instead, it worked (may check with debugger) but instead, `Nav.NavigateTo(Nav.Uri, forceLoad: true);` does not reload the pages anylonger.

### Exceptions (if any)
No, there are no exceptions.

### Further technical details

.NET SDK (reflecting any global.json): Version: 5.0.100-rc.1.20452.10 Commit: 473d1b592e

Runtime Environment: OS Name: Windows OS Version: 10.0.17763 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\5.0.100-rc.1.20452.10\

Host (useful for support): Version: 5.0.0-rc.1.20451.14 Commit: 38017c3935

.NET SDKs installed: 3.1.202 [C:\Program Files\dotnet\sdk] 3.1.402 [C:\Program Files\dotnet\sdk] 5.0.100-rc.1.20452.10 [C:\Program Files\dotnet\sdk]

.NET runtimes installed: Microsoft.AspNetCore.All 2.1.18 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All] Microsoft.AspNetCore.App 2.1.18 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 3.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 3.1.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 5.0.0-rc.1.20451.17 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 2.1.18 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 3.1.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 3.1.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 5.0.0-rc.1.20451.14 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App 3.1.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 3.1.8 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 5.0.0-rc.1.20452.2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

[ghost]

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.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.