Handle hot reload refresh when `disableDomPreservation = true`

[captainsafia]

The current resolution to #49144 in dotnet/sdk#35450 triggers an enhanced navigation to force the browser to reload a statically server-side rendered page if it has been modified by a hot reload action.

Per dotnet/sdk#35450 (comment), the experience doesn't work super well when DOM preservation is disabled. The result of this is as follows:

• For statically rendered pages, the page refresh is not triggered.
• For non-statically rendered pages, the notification UI (checkbox animation on the top left of the view) is not displayed since it is hooked onto the enhancedload event.

We should consider a fallback for this. We could trigger a page refresh on the hot reload event but this takes us back to the original dilemma of being able to determine if a given page has been statically rendered or if it has any components backed by a live rendered on it.

[captainsafia]

@SteveSandersonMS Do you have any insights on how to approach this?

if a given page has been statically rendered

I experimented with querying the page to check for any component descriptor comments but wasn't sure if that was totally foolproof.

[SteveSandersonMS]

I thought all we have to do is change Blazor._internal.hotReloadApplied in this repo so that, if hasProgrammaticEnhancedNavigationHandler() returns false, we do a full location.reload()

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.