javascript:history.back() for frame

[Ike]

Can someone show me how I can have:

<a href="javascript:history.back()" name="Back" value="Back"
style=width:40px;float:right;margin-left:0px class="button" >Back</a>

but since this href exists in a frame, it only pertains to this frame?
Thanks, Ike

[micha]

Ike wrote:

Can someone show me how I can have:

<a href="javascript:history.back()" name="Back" value="Back"
style=width:40px;float:right;margin-left:0px class="button" >Back</a>

but since this href exists in a frame, it only pertains to this frame? Thanks, Ike

using frames breaks the back function (in the sense the user expects it
to work, not in the sense of a browser crash). bear in mind that the
back button is by FAR FAR FAR the most used navigation feature - so
avoid frames.

if you insist on frames:

write your own back function - means read history content, determine
the state of each frame from that value, change the frames (using js).
but don't expect visitors to use it - they'll use the back button of
the browser - and you can't fix the frame problem there.
micha

[Randy Webb]

micha wrote:

Ike wrote:

Can someone show me how I can have:

<a href="javascript:history.back()" name="Back" value="Back"
style=width:40px;float:right;margin-left:0px class="button" >Back</a>

but since this href exists in a frame, it only pertains to this

frame?

Thanks, Ike

using frames breaks the back function (in the sense the user expects it
to work, not in the sense of a browser crash). bear in mind that the
back button is by FAR FAR FAR the most used navigation feature - so
avoid frames.

if you insist on frames:

write your own back function - means read history content,

And just how do you propose to "read history content"? Anything you do
that depends on the ability to read the history contents is doomed to
failure before you even start.
--
Randy

[micha]

Randy Webb wrote:

micha wrote:

Ike wrote:

Can someone show me how I can have:

<a href="javascript:history.back()" name="Back" value="Back"
style=width:40px;float:right;margin-left:0px class="button"Back</a>
but since this href exists in a frame, it only pertains to this
frame?

Thanks, Ike

using frames breaks the back function (in the sense the user expects it to work, not in the sense of a browser crash). bear in mind that the back button is by FAR FAR FAR the most used navigation feature - so
avoid frames.

if you insist on frames:

write your own back function - means read history content,

And just how do you propose to "read history content"? Anything you

do that depends on the ability to read the history contents is doomed to failure before you even start.
--
Randy

you're right of course. i haven't done much in javascript for a while,
so i forgot. you can't read the history. in that case you'd have to
mock up something like you own history for a solution of the frame
problem - which definitivly won't be reliable and a lot of hassle. so
it all boils down to what i tried to make clear in my 1st post - don't
use frames.
i found that about any functionality frames provide can be replaced
very well by some kind of template system, i.e. for navigation and
logo.

micha

[Thomas 'PointedEars' Lahn]

micha wrote:

Ike wrote:

Can someone show me how I can have:

<a href="javascript:history.back()" name="Back" value="Back"
style=width:40px;float:right;margin-left:0px class="button" >Back</a>

but since this href exists in a frame, it only pertains to this
frame? Thanks, Ike

using frames breaks the back function (in the sense the user expects it
to work, not in the sense of a browser crash).

It does not, as the history of the frameset window consists of the combined
histories of every frame. However, users that are not aware that they are
using a frameset may be confused by the normal behavior.
PointedEars