Hi,
When I add a window with a draggable containment that changes with browser resizing the kendo window is limited to the containment elements original browser size.
1. run the example with a small browser window.
2. resize the browser to make it bigger.
3. try to resize the kendo window to make it bigger, it will not get bigger than the original containment size.
https://dojo.telerik.com/axuRUkiq/3
Is there an initialization function that I can call to reset the containment? I can kind of fix it by setting the maxHeight, maxWidth options on the window resize.
Thanks.

I've hit this issue as well - 7 years later and its still not fixed!
Centering and resizing of a contained window only takes account of the initial size of the container, not its current size. This can lead to the window's maxHeight and maxWidth being set to wildly wrong values - zero in my case - making the windo open and center into completely the wrong place.
I've found that adding a window.setOptions( {maxHeight:Inifinity, maxWidth:Infinity}) before doing an window.open() and/or window.center() makes it work correctly, as it forces a re-evaluation of the containment's current dimensions.
The Kendo UI Window component currently does not provide a dedicated initialization function to reset containment constraints or force a re-evaluation of the container size after the initial setup. The behavior you observed—where maxHeight and maxWidth are calculated only during initialization—can indeed cause issues if the container size changes dynamically.
Your approach of calling:
window.setOptions({ maxHeight: Infinity, maxWidth: Infinity });If you need the Window to stay responsive to container or browser resizing, you can enhance your solution by binding to the resize event:
$(window).resize(function() { var wnd = $("#window").data("kendoWindow"); wnd.setOptions({ maxHeight: Infinity, maxWidth: Infinity }); wnd.center(); });Currently, there are no alternative built-in methods to reset containment constraints dynamically, so your workaround is the recommended approach given the widget’s limitations.
If you have further questions or need more guidance on handling specific scenarios, please let me know.