Fix use of ReconnectModal in Blazor templates with auto mode and global interactivity #60735
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes two issues with
ReconnectModal
in the Blazor project template:--interactivity auto
and--all-interactive
(aka global interactivity) use different file structure. This fixes theReconnectModal.razor.js
include path in this case, as reported in https://github.com/dotnet/AspNetCore-ManualTests/issues/3482 (after closing the original issue).<ReconnectModal>
element inMainLayout.razor
does not work with global interactivity. This moves the element toApp.razor
and updates the import statements in_Imports.razor
accordingly, so that the JS code setting up reconnection event handlers is executed properly in all modes.