NavigationManager issue when using in ModalService about ant-design-blazor

[zxyao145]

@MaggiGorengAyam

Because the timing of triggering NavigationManager.LocationChanged is different between asynchronous and synchronous methods.
Dialog will clean up the DOM when NavigationManager.LocationChanged, In the synchronization method, Dialogs first clean up the DOM, and then Blazor will clean it up; In asynchronous method, Blazor will first clean up the DOM, then the component is deleted, and the listening for NavigationManager.LocationChanged in the Dialog will become invalid.

A temporary solution is to cancel the closure of Confirm and hand over the clearance of DOM to Antd:

ModalService.Success(new ConfirmOptions()
    {
        Content = "Test using Nav Manager in modal service of ant blazor",
        OnOk = (e) =>
        {
+            e.Cancel = true;
            GoBack();
            return Task.CompletedTask;
        }
    });

This bug will be fixed as soon as possible.

[zxyao145]

@MaggiGorengAyam Hi, thank you for your feedback. After 0.17.3, we added the handling of NavigationManager.LocationChanged to clean up some DOM, which in some cases conflicted with the Blazor framework.

[MaggiGorengAyam]

@zxyao145 Noted. How will this work going forward? Is there a way this should be handled? Any reason why the async version works but not the non-async?