Tell it to Microsoft... :) My suggestion would be to kill the selects and go with a dhtml lookalike dropdown. You can maintain the separation between your UI elements, without getting crazy with detecting where your elements are onscreen.
-- jon mailto:[EMAIL PROTECTED] Monday, June 2, 2003, 12:21:39 PM, you wrote: w> OK thanks everyone, but I think I didn't ask the question correctly!! w> It is true you can usually stick in a fix to avoid issues. But I'm a nerd w> and as a nerd, I never (well nearly never) allow this kind of tight w> couple-ing in an app. IMHO an element like a menu should be responsible for w> it self. So in these case, the menu should be responable for dispaying w> properly. w> So in my world w> A menu hiding stuff under it to display = fine. (it has focus, the gui is w> behaving correctly) w> A select hiding itself if its under an open menu = crap. (it doesn't have w> focus, it doesn't carea about the menu) w> This kind of stuff makes it harder in the short term but means that the menu w> is self contained. If the main content of the page is changed later (and the w> menu remains the same) i want the menu to still work even if I add or remove w> a select from the page... w> Hope that clarifies my (nerdy) position :-) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. http://www.cfhosting.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
