If I were you, I'd remove the feature altogether. The main reason is that some of those 'biographies' need to be scrolled to view in full (add a scrollbar; enlarging the frame isn't good enough). However, to do that the user would need to move their mouse (most people don't navigate with the keyboard, after all), and unless the user is willing to purposefully avoid all of the other images, they will trigger a change. Very bad.
If you must persist, then use the frames collection of the window object:
Code:
function loadFrame(link) {
window.frames[link.target].src = link.href;
}
<a href="..." target="teampop" onmouseover="loadFrame(this);">...</a>

Originally Posted by
simonf
Yep... would you believe customer wanted it sliced.. beleives it to be faster!!!
You're the one being used for your expertise, are you not? So tell them that in your opinion, as the expert, that they don't know what they're talking about (you'll want to use a little more tact than that
).
Multiple images mean multiple requests. If persistent connections aren't used, that also means more connections, and more load on the server. Faster? Not a chance. It might seem faster as you can see parts of the image before the entire thing has downloaded, but you can get a similar effect with progressive encoding.
Mike
Bookmarks