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.
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.
Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic. Our thoughts here at Progress are with those affected by the outbreak.
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.
UI for Blazor
Posted on:23 Sep 2019 14:24
I would not have used Window control as content for a Window.
I don't see the need for that scenario as you pointed out.
The window content of the parent window being a component that contains a nested window is where I had an issue.
My nested component had other content in addition to a Window that was displayed as the result of clicking an option to display additional detail.
I have modified our architecture to not use multiple nested windows as this seems to go against the intended/normal use of a sub/modal window.
If the error resurfaces under our new architecture I will report it.
Thanks for your assistance.
Posted on:22 Sep 2019 10:44
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.
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).