Welcome to WebmasterWorld Guest from 54.161.228.30

Forum Moderators: incrediBILL

Message Too Old, No Replies

   
2:01 am on Oct 16, 2001 (gmt 0)

10+ Year Member



In earlier versions of Netscape, and in IE, you could have a link that acted as a "Back" button, by using the javascript history.back().

Now it seems that it doesn't work in Netscape 6.

Does anyone know of a workaround so I can still use the "Back" functionality?

(I have looked around, it seems to be a Netscape 6.1 "bug" .. but I couldn't see any workarounds).

Cheers.

2:24 am on Oct 16, 2001 (gmt 0)

WebmasterWorld Senior Member macguru is a WebmasterWorld Top Contributor of All Time 10+ Year Member



Hello Misao,

Welcome to WmW. I bet you will like this site.

<a href="javascript:void(history.go(-1))"> </a>

Enjoy!

4:10 am on Oct 16, 2001 (gmt 0)

10+ Year Member



Cheers, that worked great.
6:07 am on Oct 16, 2001 (gmt 0)

10+ Year Member



I spoke too soon ....

It seems to work the first time you click on the link, but then it stops working.

It's like Netscape loses it history or something....

I am using this on a frames site, though the frame that I want to go back, is the same frame that I am calling the js from..

I also tried (a href="javascript:parent.content.history.go(-1)") but that only worked the first time as well ...

Ideas?

1:07 pm on Oct 16, 2001 (gmt 0)

WebmasterWorld Senior Member macguru is a WebmasterWorld Top Contributor of All Time 10+ Year Member



Oops! Now we need some real help. Thanks for mentioning about frames. Hopefully, some real JavaSript guru will show up with more details or better a solution.

What kind of target was the first call in history? _main, _parent, or may be a custom frame name?

2:59 am on Oct 17, 2001 (gmt 0)

10+ Year Member



Well, I put some pages togther with just skeleton code on it, in the same format etc (so I could see if it was being affected by posts and stuff), and I still encountered the same problem.

I even tried uninstalling NS 6.1, and installing mozilla instead, and it had the same bug (tried it on another machine as well, and it was reproducable). But strangley enough, I had someone who runs mozilla on a nix machine, and he could not reproduce the behavour. So I'm thinking that it is a windows/ns bug, and it has been fixed in the nix version.

Ah wells, I guess that browser bugs are out of the scope of the system, though it is still annoying, and I would love to know an easy workaround for it.