.Net 10 Blazor Enhanced Navigation in WASM fails due to no PageTitle #64522
Description
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
Description:
Navigating from InteractiveWasm route to a Static/InteractiveWasm route fails.
In the reproduction app, clicking Counter and then Home → navigation error.
In the Chrome console, an error appears: "InsertBefore issue" in blazor.web.js
Regression:
This works fine in DotNet 9.0; the error appears in DotNet 10.0.
Workaround I
A temporary workaround is to force a full reload via NavigationManager.NavigateTo(url, forceLoad: true).
Workaround II
Another workaround is downgrading back to .NET 9, but ideally we would continue on .NET 10.
Expected Behavior
Navigate smoothly to new page. Instead, error occurs in console. Url in address bar changes, but no new page is shown.
Steps To Reproduce
For easy reproduction: a repo with 2 simple identical projects -- one for dotnet 9 and one for dotnet 10:
BlazorApp_Navigation_InsertBefore_Error
To reproduce the OK and the NOK version:
- Load the .NET 9.0 version in VS2022 and run it. Follow the steps on the home page → OK.
- Load the .NET 10.0 version in VS2026 and run it. Follow the steps on the home page → NOK.
.NET Version
10.0.100
More info
Based on identical error, this bugreport was initially added to the following issue:
.NET 10 Blazor navigation from wasm to interactive server broken (#64472)
Update
After further efforts to find the difference between working and problematic pages, I found the following:
If a page does not have a PageTitle tag, it shows in the browsertab localhost:xxx/somename, from that moment on the nav is broken.
Workaround III
Add a PageTitle tag: SomePageName
Update
This PageTitle issue is different than the previous issue: .NET 10 Blazor navigation from wasm to interactive server broken (#64472)
So, this No-PageTitle issue is now created for this specific issue .