Having just posted my previous message about the WebDialog and WebDateChooser, I thought I would try the WebDialog with a WebCombo.
I again created a simple web page with a single button to display the WebDialog. In the WebDialog I placed a WebCombo bound to an SQLDataSource linked to a single table with three columns.
Clicking the button displays the WebDialog and the WebCombo. Clicking the drop down for the WebCombo appears to do nothing, but closing the WebDialog leaves the drop down portion of the WebCombo displayed.
Click the selection in the drop down and it disappears. Then again click the button to bring up the WebDialog, and the WebCombo is showing the selection you have just made.
Note that I have tried placing a standard dropdownlist control on the WebDialog, and this works just fine !!!
Will I have the same problems with all Infragistic controls that have some form of drop down ?
Surely someone tried basic testing such as this before releasing the latest version.
I await comments.
I have just tried the same experiment but instead using a UltraWebMenu control in the WebDialog.
Again the menu control does not display any of the drop down sub menus.
Just when I thought that the WebDialog would solve many of my problems !!
function pageLoad(args){
$IG.DialogMoveBehavior.prototype._doZ=function(lid, elem, lidZ){ this._newZ = this._oldZ = $util.getStyleValue(null, 'zIndex', elem); if(!lidZ) lidZ = $util.toInt($util.getStyleValue(null, 'zIndex', lid), 0); if(lidZ < 10) lid.style.zIndex = lidZ = 100; //z-index will default to 100 in a modal scenario if($util.toInt(this._oldZ, 0) <= lidZ) elem.style.zIndex = this._newZ = lidZ + 1; return lidZ;};
}
Check the z-index of the dialog (and the dropdown or menu). The dialog needs to display 'on top' of everything, so it's given an enormously high default z-index. The dropdown portion of any non native dropdown control is an absolutely positioned container which also must get displayed above everything else. It sounds like the Dialog Window is set to a z-index which is higher than the dropdown portion of the webcombo and webdatechooser (which I think use 1000). Choosing which control ultimately displays on top is a matter of setting the z-index. The reason the classic HTML Select 'works' is because it's a native control to the browser which is actually a separate window. Ever try to get an HTML element to appear over top of the HTML Select.. ? Not fun. virtually impossible without a buch of messy hacks.
Anyway, to remedy your scenario you'll want to set the DialogWindow's z-index to a value lower than the dropdown, or set the dropdown's z-index higher than the DialogWindow. Both can be set using the controls css class, and the z-index property. I'll check with the product team and see if there's a reason we can't default this to something that will work better with other controls without forcing you to manually adjust the z-index.
-Tony