I was a bit thrown off by this because I didn't think we'd changed anything that would be likely to affect this. Upon verifying, this does still repro for me on master. Is it possible that it doesn't repro within the E2E project because it doesn't have a top-level <Router>, and hence it's trying to do server-side navigation?

For clarification here's what reproduces the issue for me: https://github.com/dotnet/aspnetcore/compare/stevesa/blur-bug-repro. Apologies for the ambiguity/typos in the original bug report.

I was a bit thrown off by this because I didn't think we'd changed anything that would be likely to affect this. Upon verifying, this does still repro for me on master. Is it possible that it doesn't repro within the E2E project because it doesn't have a top-level , and hence it's trying to do server-side navigation?

Hm. I'll check on this. I validated inside the test harness and in a new standalone WASM project using 5.0-dev bits. I'll give your repro ago in case I missed something.

@SteveSandersonMS Woop. You're right. I'm able to repro this on a standalone app with the 5.0.100-rc.1.20405.4 SDK so it's definitely still an issue. I'll investigate and push a fix to this PR.