I'm thinking about a design where I maintain a URL stack in a session
variable that stores where a user has been, so that clicking a back
button (not the browser's) will take a user to the right place. It would
work like this: Click a Continue button - Push a new URL onto the
stack, and take the
:[EMAIL PROTECTED]]
| Sent: Monday, September 23, 2002 8:43 PM
| To: '[EMAIL PROTECTED]'
| Subject: [OT][WORKFLOW] Any best practice for back, save,
continue
| buttons?
|
| I'm thinking about a design where I maintain a URL stack in a session
| variable that stores where a user has been, so
| -Original Message-
| From: Dan Cancro [mailto:[EMAIL PROTECTED]]
| Sent: Monday, September 23, 2002 8:43 PM
| To: '[EMAIL PROTECTED]'
| Subject: [OT][WORKFLOW] Any best practice for back, save,
continue
| buttons?
|
| I'm thinking about a design where I maintain a URL stack in a session
| variable
][WORKFLOW] Any best practice for back, save,
continue buttons?
I'm thinking about a design where I maintain a URL stack in a
session variable that stores where a user has been, so that
clicking a back button (not the browser's) will take a user
to the right place. It would work like
I'm thinking about a design where I maintain a URL stack in a session
variable that stores where a user has been, so that clicking a back
button (not the browser's) will take a user to the right place. It would
work like this: Click a Continue button - Push a new URL onto the
stack, and take the
:[EMAIL PROTECTED]]
| Sent: Monday, September 23, 2002 8:43 PM
| To: '[EMAIL PROTECTED]'
| Subject: [OT][WORKFLOW] Any best practice for back, save,
continue
| buttons?
|
| I'm thinking about a design where I maintain a URL stack in a session
| variable that stores where a user has been, so
| -Original Message-
| From: Dan Cancro [mailto:[EMAIL PROTECTED]]
| Sent: Monday, September 23, 2002 8:43 PM
| To: '[EMAIL PROTECTED]'
| Subject: [OT][WORKFLOW] Any best practice for back, save,
continue
| buttons?
|
| I'm thinking about a design where I maintain a URL stack in a session
| variable
][WORKFLOW] Any best practice for back, save,
continue buttons?
I'm thinking about a design where I maintain a URL stack in a
session variable that stores where a user has been, so that
clicking a back button (not the browser's) will take a user
to the right place. It would work like
Cancro [mailto:[EMAIL PROTECTED]]
| Sent: Monday, September 23, 2002 8:43 PM
| To: '[EMAIL PROTECTED]'
| Subject: [OT][WORKFLOW] Any best practice for back, save,
continue
| buttons?
|
| I'm thinking about a design where I maintain a URL stack in a session
| variable that stores where a user has been
publishing
| -Original Message-
| From: Dan Cancro [mailto:[EMAIL PROTECTED]]
| Sent: Monday, September 23, 2002 8:43 PM
| To: '[EMAIL PROTECTED]'
| Subject: [OT][WORKFLOW] Any best practice for back, save,
continue
| buttons?
|
| I'm thinking about a design where I maintain a URL stack
][WORKFLOW] Any best practice for back, save,
continue buttons?
I'm thinking about a design where I maintain a URL stack in a
session variable that stores where a user has been, so that
clicking a back button (not the browser's) will take a user
to the right place. It would work like
Ahhh yes, the bane of web app developers! I solved this problem with
JavaScript and cookies - no browser back operations allowed!
And spare me the what if JavaScript is turned off noise - it just doesn't
happen in the REAL world.
Mark
-Original Message-
From: Andrew Hill
20:04
To: 'Struts Users Mailing List'
Subject: RE: [OT][WORKFLOW] Any best practice for back, save,
continue buttons?
Ahhh yes, the bane of web app developers! I solved this problem with
JavaScript and cookies - no browser back operations allowed!
And spare me the what if JavaScript is turned
PROTECTED]]
Sent: Tuesday, September 24, 2002 20:04
To: 'Struts Users Mailing List'
Subject: RE: [OT][WORKFLOW] Any best practice for back, save,
continue buttons?
Ahhh yes, the bane of web app developers! I solved this problem with
JavaScript and cookies - no browser back operations allowed
-Original Message-
From: Galbreath, Mark [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 25, 2002 00:10
To: 'Struts Users Mailing List'
Subject: RE: [OT][WORKFLOW] Any best practice for back, save,
continue buttons?
you might find a work-around using hidden fields, but I've attached the two
to be on?
/ten-second-assesment
-Original Message-
From: Galbreath, Mark [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 25, 2002 00:10
To: 'Struts Users Mailing List'
Subject: RE: [OT][WORKFLOW] Any best practice for back, save,
continue buttons?
you might find a work-around using hidden fields
I'm thinking about a design where I maintain a URL stack in a session
variable that stores where a user has been, so that clicking a back button
(not the browser's) will take a user to the right place. It would work like
this:
Click a Continue button - Push a new URL onto the stack, and take
17 matches
Mail list logo
