Tim,
I haven't tried Netscape because this is an intranet only application and everyone on our network uses IE (it's the standard). I can try it on Netscape, though, just to see how it behaves.
Could this have anything to do with JavaScript 1.2 on IE 6? Just a thought. . .
One of the developers I work with has found a workaround. While it seems to solve the problem, I still don't understand why it is necessary to modify my code in order for it to run correctly on IE 6. If anyone has an idea, please let me know. I don't like doing workarounds. You will see the workaround in bold below. I have tried to strip this code down to the bare minimum that
you should need to see. If you want, I can post the entire code, but it is quite lengthy.
In the parent frame, SelectList.jsp:
<script language="JavaScript"><!--
var reloaded = false;
function reloadOnceOnly()
{
if (!reloaded)
{
reloaded = true;
window.detailframe.history.go(0);
}
}
//--></script>
In the top frame Buttons.jsp (where the <select> box exists called pointOfCare):
In the bottom frame List.jsp (where the the data will sometimes change to the data that it should display, and then refresh and revert to display the data that was there before the value was changed):
<BODY onLoad="parent.reloadOnceOnly()">
Again, if anyone has any ideas why I have to add special code in order for it to run in IE 6, I'd really appreciate it. Thanks for your help.
[This message has been edited by verduka fox (edited November 15, 2001).]