|
|
Posted by David T. Ashley on 04/09/06 20:18
"Jiri Fogl" <xfoglj00@stud.fit.vutbr.cz> wrote in message
news:e1akkt$knc$1@boco.fee.vutbr.cz...
> The best advice is probably not to use frames - there are more problems
> with them (i.e. accessibility - browse through framed page with cell phone
> is a nightmare).
>
> If you must use them, try using cookies or sessions. Every page in main
> frame saves its name to the session or cookie. Main page (the one with
> <frameset> and <frame> tags) will read this information and write the
> appropriate src attribute of main frame.
>
In a logical sense, I agree with you ... the behavior of the browser is not
guaranteed and it should reload the frameset.
The mystery to me is why Internet Explorer is apparently able to make such
good guesses most of the time.
For example, if you go to this web site:
http://www.metzgersaircraft.com/
and try the links on the left navigation bar (with Internet Explorer), then
use reload, you'll notice that it reloads the main frame as expected. I
know for sure that this site does not use cookies for frame status (I helped
them set it up). I can cite other sites with frames that behave the same
way with IE. (For example, http://webtools.e3ft.com/ and try the "htpasswd
generation" and then reload.)
So, IE is using cues that I'm not understanding to take a good guess ... but
it doesn't work on the development site I'm playing with. The question is
why.
Thank you for the suggestion about the cookies. That will definitely do the
trick if I can't figure out why IE works the way it does (and it is probably
better as it would work on other browsers, too). That suggestion will
definitely cure my problem. But the mystery remains ...
Thanks, Dave
Navigation:
[Reply to this message]
|