Pop It menu being hidden by list box in .net app

[swordstaind]

so I'm using the Pop It Menu on my site. and I have a couple of list boxes that need to be there.

the problem is that when I mouse over the menu half of it is being hidden behind the list box. I looked around for other fixes and found a previous thread with a similar problem but changing the z-index like it suggested does not work in this instance is there any way to fix this or do I need to get a different menu?

Thanks for the help

[jscheuer1]

As I recall, this is only a problem in IE. If that is the case yes, more than z-index is required to fix it. I'm not certain what you mean by a 'list box', I imagine you mean a select tag or some other form element. If this is the case, code needs to be added that will render the offending element invisible (hidden) while the Pop It is being displayed and then make it visible again when the Pop It disappears. In general, you give an id to the element or use its existing one if it has one and in the code where the Pop It is revealed add a line (shown in red):

function showmenu(e, which, optWidth){
if (!document.all&&!document.getElementById)
return
document.getElementById('id_of element').style.visibility='hidden'
clearhidemenu()

Then where the Pop It disappears:

function hidemenu(){
document.getElementById('id_of element').style.visibility='visible'
if (window.menuobj)
menuobj.style.visibility="hidden"
}

If you have more than one element you need to hide/show, use additional lines. Refinements can be made so that only certain Pop Its will activate this extra code and it can be made so that browsers that do not need the extra code will ignore it but, the above is the general idea. To be more specific, I'd prefer to see your page:

PLEASE: Include the URL to your problematic webpage that you want help with.

[swordstaind]

a list box is an asp.net control sort of like a dropdown list but with more options visible. changing the visiblity of the list box on mouse over of the menu is not a valid option at this point.

It turns out this is a bug with asp.net framework so there's really no way around it thanks for the help though.