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.
Hello Guy,
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. Unless you make the position absolute it should be relative to the container that it is in. Which is why the BodyAsParent property exists because the WebDialogWindow could be larger than its container.
Please let me know if you have any further questions concerning this matter.
Well right now the initial position is set to centered and this puts it in the center of the browser window not the container. Causing the top portion of the window to be culled in some instances. I am looking for a way to center it along the X-Axis and have it ensure it is low enough on the Y-Axis to be within the content pane of the tab in which it was opened.
Thank you for the update. The WebTab doesn’t have a way to get a position of the WebTab or its container. You will want to determine the position of the WDW yourself by seeing what is on your page and seeing what positions work.
I am following up to see if you have any further questions concerning this matter.
Please let me know if I may be of further assistance with this matter.
This is still Guy, I have had to move onto my companies account as support ended for mine on 6/6.
We are still having the same issues with the WebDialogWindow and have yet to find a suitable workaround. It worked perfectly before when contained within an UltraWebTab. I did notice that although the UltraWebTab was listed as a retired control it is still in the help docs for v14.1.
Does this mean that the UltraWebTab will still function when upgraded to v14.1?