| 8:53 am on Oct 31, 2000 (gmt 0)|
Here's [grizzlyweb.com] a script that says it will do what you want. The page offers two versions of framebuster code. Version 1 -- the longer one -- maintains an intuitive history list.
By the way, I was thinking about your "wish" to be able to change browser history -- that would certainly open some outrageous security holes, wouldn't it! Sort of like my pet wish to be able to view a browser window's history when someone visits. Not gonna happen, I'm pretty sure.
I probably wouldn't like what other sites would think up to do to me in such a world anyway.
[marker rcjordan frames js]
Edited by: rcjordan
| 9:13 am on Oct 31, 2000 (gmt 0)|
Cheers for the link, but each of these scripts create the different problems I am aiming to avoid.
The first clears the history, therefore greying out the back button.
The second causes the really annoying bouncing behaviour.
I'd love to have no impact at all on the back button's use. Any page that fiddles with it just winds me up no end.
| 11:15 am on Oct 31, 2000 (gmt 0)|
If you come across what you're looking for, please post a followup.
| 1:09 pm on Oct 31, 2000 (gmt 0)|
>>The first clears the history, therefore greying out the back button<<
I only see that behavior if I just opened a new window and the history list is only 1 location long.
Have you tried something along these lines:
if (parent !== self)
I just tested it in Netscape Communicator 4.7 and Explorer 5.5 -- it works on this machine.
| 1:20 pm on Oct 31, 2000 (gmt 0)|
I made the schoolboy error of trying to maintain a browser history that wasn't there.
Fantastic, that's being bugging me for days! :)