I'm not sure I understand exactly what you're doing - but I think I understand a bit. Instead of DIVs have you tried IFRAMEs to obtain similar functionality?
H. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Adrian Cho Sent: 23 March 2003 11:22 To: [EMAIL PROTECTED] Subject: [MVC-Programmers] Problems with Select in Divs Refs http://www.experts-exchange.com/Web/Web_Languages/Q_20488024.html http://www.experts-exchange.com/Web/Q_20396305.html http://www.milonic.co.uk/menu/overforms_sample.php I had a lot of problems using selects in web pages with div layers. I thought you might want to know it is a problem with browsers. (See links, problems reported by other developers) In one project of mine, the page design was that each div displays a jsp, which has a supporting action class. When an item is listed, a javascript function calls the action classes (7 of them in total) to display the jsps. All the html elements are displayed properly except SELECTs. Orignially I thought it was a good web page design because all the action classes are running in parallel to retrieve data. The user can click and select the div layer to view the data as soon as it is available. Also there is no more Http post (web traffic) while the user switches between "div views" of different data. The web page designer and project manager, well everyone in fact, thought it was a very good idea. So we "stuck" with the web page design even though we knew there was a problem in browser displaying SELECT. Guess what, like everyone said, let us spend a little effort to get SELECT working. In the end, it took three months developing our own SELECT option. Still there are problems here and there. One example is with request.getParameters(). With hindsight, I would say maybe it would be easier to re-disign the pages. But I must admit I still like the original idea of displaying different view data in div layers to avoid http post traffic. Guess I can't have the cake and eat it at the same time. If the problem is fixed in the future version of browsers, a lot of the existing code may be broken in projects of other people too. It is a long story. One reason is due to z-index set to be infinity. I thought you might want to read the links and experiment yourself. Maybe, just maybe, someone can find a better solution and we would all benefit. Or, one may say, let us re-design the pages :) _______________________________________________ MVC-Programmers mailing list [EMAIL PROTECTED] http://www.basebeans.net:8080/mailman/listinfo/mvc-programmers _______________________________________________ MVC-Programmers mailing list [EMAIL PROTECTED] http://www.basebeans.net:8080/mailman/listinfo/mvc-programmers
