Using javascript.location.replace() to remove back-button problem s

[Uriah Carpenter <ur...@widen.com>]

According to David Flanagan, in _JavaScript, The Definitive Guide 4th
Edition_, JavaScript's location.replace() method will NOT create a new entry
in the history object. I believe, this means that if you were to solely use
this method of nagivation around your app, you would only have ONE page in
the history (the current page), and no back button issues to worry about.
 
Has anyone every tried having a Tapestry app using only the Javascript
location.replace() method to navigate between pages to prevent "back-button"
horrors?
 
-- Uriah

Re: Using javascript.location.replace() to remove back-button problems

[Programozás <pr...@hotmail.com>]

This trick does not work with form submits.
If you have no forms in your application then you have solved the backbutton
problem :)

Norbi

----- Original Message ----- 
From: "Uriah Carpenter" <ur...@widen.com>
To: <ta...@jakarta.apache.org>
Sent: Monday, March 08, 2004 11:21 PM
Subject: Using javascript.location.replace() to remove back-button problems


> According to David Flanagan, in _JavaScript, The Definitive Guide 4th
> Edition_, JavaScript's location.replace() method will NOT create a new
entry
> in the history object. I believe, this means that if you were to solely
use
> this method of nagivation around your app, you would only have ONE page in
> the history (the current page), and no back button issues to worry about.
>
> Has anyone every tried having a Tapestry app using only the Javascript
> location.replace() method to navigate between pages to prevent
"back-button"
> horrors?
>
> -- Uriah
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org