|
Posted by James on 10/20/02 11:14
Currently I have an application with PHP scripts that passes POST
variables to keep track of ID's of records, the processing mode and
such.
I totally didn't design it to handle when a user hits the Back button
in the browser...everything is tightly controlled...The user clicks
on links/buttons to take actions.
So far the database updates are fine and almost everything behaves
correctly when the user hits the back button. However, I do have one
page that shows a list of records. The user clicks "Edit" and the
list is shown again, but this time with the selected record as
Editable fields. If the user presses the Browser's Back button, the
record still appears as Editable. This is just one of those cases.
What have people done in the past to deal with states and such and
keeping these things straight when the user hits the BACK button?
-James
--
Navigation:
[Reply to this message]
|