I am aware that the UseBodyAsParent property does not work on a webdialogwindow inside an update panel. However, not using an updatepanel is not an option is this case yet I still need to at least emulate this behavior.
The issue is that the WebDialog window exists inside a WebTab inside a Webtab which is inside an updatePanel. The update panel is a required element and as such cannot be removed. When the WebDialog Window displays it is contained within it's webtab, the problem here is if the webdialog window is larger than the webtab's content area or if the user's screen is small enough then any part of the webdialog window which extends beyond the content area is lost. I have run a little test of disabling the update panel and using usebodyasparent and that does exactl what I need. However the property does not work with the update panel enabled and the update panel must be enabled for full functionality of the site.
The Reason the Update panel is required is for another set of third party controls and the reason I cannot remove the WebDialogWindow from the update panel is because the page much have an overall update panel for the other third party controls to function correctly.
Thank you for contacting Infragistics!
I have done some looking into this matter and have some questions. What do you have in the WebDialogWindow? Have you tried setting the WebDialogWindow or the controls you have in it as triggers on the UpdatePanel when you have it outside the UpdatePanel?
We have many WebDialogWindows, all of which will be contained inside tabs. None of which are loaded until the usercontrol is loaded inside the tab. I did attempt adding the buttons which display the webdialog window as triggers on the update panel.
I cannot have the webdialog outside of the update panel as it is contained in the usercontrol inside of the WebTab inside of the update panel. When I tested it without the update panel I simply removed the update panel from the page however this causes many other controls to cease functionality.
Thank you for the update. Instead of wrapping the Update Panel around the whole page can you just wrap it around the controls that require it to function? Possibly having multiple update panels depending on how your controls are laid out?
I would love for that to be the case. The issue is that these other third party controls have features which have to be enabled on loading on the initial page and require a single update panel that encompasses the controls for these features to work. Our project is constructed in such a way that we only have a single page and everything else is user controls and so this means that removing the main update panel with cease functionality of these other third party controls which are quite heavily integrated into our system.
Thank you for the update. The UseBodyAsParent property isn’t supported when the WebDialogWindow is in an UpdatePanel or other asynchronous postback container:
You can move the WebDialogWindow outside of the UpdatePanel or you can make the container the WebDialogWindow is in larger.
Please let me know if you have any further questions concerning this matter.