Hello,

This manifests when adding an Editor in the Window, because the Editor uses some Windows internally. You can find attached to this post a workaround for that - it mimics a Window through an AnimationContainer.

Something similar might be a workaround for other cases too.

Regards,
Marin Bratanov
Progress Telerik

To add some context for a valid use case - a grid that has PopUp edit mode that is within a Window. At the moment, this prevents the first window from the grid from showing up altogether, and to get this to work you need to switch the grid to InLine or InCell edit mode.

Regards,
Marin Bratanov
Progress Telerik

Thank you for getting back to me, Mark. Nesting modal windows is, indeed, a bit of a gray area. For one, the accessibility standards do not offer anything in this regard. There is a feature request in this regard that we will investigate at some point, and you may want to Follow and/or Vote for it: https://feedback.telerik.com/blazor/1407791-support-for-multiple-nested-modal-windows.

Having several non-modal windows open at a time is, however, something that should work and be supported. While there is some work to be done in this case (for example, handing z-index and activation), on my end this seems to work in the general case I tested. We would like to ensure that it works in your case too, so if you do have problems with that, don't hesitate to send us the details so we can look into it.

With that said, I am now going to close this particular issue because we can't reproduce a problem in a valid use case. If a problem surfaces with another case, let's discuss it then.

Regards,
Marin Bratanov
Progress Telerik

Hi again Mark,

While I was able to reproduce this when the window is declared directly in the window, having a component between them seems to work fine for me. I am attaching a test case so you can see whether you have a similar situation. Can you modify it to showcase the problem?

I am also attaching the original test where I reproduced the problem, but it is not going to be considered a valid use case - if the two windows are children of the same component, you must declare them next to each other.

I will be looking forward to your feedback so we can try to have a valid bug fixed for our next release.

Regards,
Marin Bratanov
Progress Telerik

Hello Mark,

In the 2.0.0 release the window now renders at the root of the app (where the TelerikRootComponent is) and it seems this is causing the nesting problem. I am logging this for investigation and you can Follow this page for status updates. At the moment, I can't offer any workaround (apart from, of course, not nesting windows, but I am not sure if this is feasible).

Regards,
Marin Bratanov
Progress Telerik