search

dotnet / aspnetcore

ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
https://asp.net
MIT License
35.57k stars 10.05k forks source link

Disable navigation interception if the interactive router gets removed from the page #50069

Open MackinnonBuck opened 1 year ago

MackinnonBuck commented 1 year ago

If an interactive router gets dynamically removed, server-side routing doesn't take over again, and each navigation updates the address bar without changing any content on the page.

Disabling navigation interception when the router gets removed would allow server-side routing to work again.

This was prototyped in https://github.com/dotnet/aspnetcore/pull/50012 as part of an unrelated feature, but that PR got closed in favor of a more narrowly-scoped one.

ghost commented 1 year ago

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

javiercn commented 1 year ago

@MackinnonBuck is this still relevant?

MackinnonBuck commented 1 year ago

@javiercn It's still an issue, yes. I implemented a fix in https://github.com/dotnet/aspnetcore/pull/50564, but we closed it as not a priority for .NET 8.

ghost commented 11 months ago

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.