-
Would it be possible to keep a dialog open even if the route changes. A simple example would be: await DialogService.ShowDialogAsync(@<div>
<FluentButton OnClick="@(() => NavigationManager.NavigateTo("/"))">Home</FluentButton>
<FluentButton OnClick="@(() => NavigationManager.NavigateTo("/other"))">Other</FluentButton>
</div>
, new DialogParameters
{
Title = "Dialog that changes the route",
}); All dialogs are rendered inside a "global" DialogProvider, therefore this should be possible I think. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
The question is not only about the DialogProvider, which is global and contains the HTML content, but also about whether the references to the objects that open this window are still in memory ( What's more, ergonomically speaking, I don't think this is a good thing in a “Web” world. Currently, it's not possible to do this as standard in FluentUI Blazor d components. |
Beta Was this translation helpful? Give feedback.
The question is not only about the DialogProvider, which is global and contains the HTML content, but also about whether the references to the objects that open this window are still in memory (
DialogService.ShowDialogAsync
). And this is probably not the case.It's therefore quite complicated to keep all these objects in memory when a page is changed.
What's more, ergonomically speaking, I don't think this is a good thing in a “Web” world.
Currently, it's not possible to do this as standard in FluentUI Blazor d components.