Yeah this is an IE problem I ran in to a few years ago with IE 5.0 that
still lives today. Back then I found an IE white paper that basically just
said that they had trouble with monitoring nested frame progress. There was
no convenient method to avoid this but I did find some work arounds. Not
sure what will work exactly for you but you should try:
1) Adding the void(0); method call in your javascript href (<a
href="javascript
:EditDatabase(3);void(0);">)
2) set the iframe2.href property instead of the src property
3) once iframe2 has completed loading, make a call to a 3rd iframe and set
the href to about
:blank
In my case I was using the iframe to move databack and forth so after I was
done moving the data I just set the iframe to about
:blank and this worked
for me. Hopefully you'll find a convenient solution for your project. Too
bad Microsoft just doesn't fix this.
"Steve - DND" <ng@digitalnothing.com> wrote in message
news:vr************@corp.supernews.com...
There has to be an answer out there somewhere for this, but I couldn't
find it in Google anywhere. I have a page with two IFrames. In IFrame#1 I have
a link that looks like so: <a href="javascript:EditDatabase(3);">Edit</a>
When this link is clicked it fires the EditDatabase() function which finds
IFrame#2 by going up to the parent and getting IFrame#2 from there. It
then does IFrame2.Src = "Database.aspx?ID=3";
This part of the process works fine and the page loads. However, IE still
appears to be loading because the progress bar at the bottom slowly make's
it's way across the screen. Is there any way I can stop this from
happening?
Thanks,
Steve