You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by "Galbreath, Mark" <Ga...@tessco.com> on 2002/09/24 14:04:01 UTC
RE: [OT][WORKFLOW] Any best practice for "back", "save", "continu
e" 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 off" noise - it just doesn't
happen in the REAL world.
Mark
-----Original Message-----
From: Andrew Hill [mailto:andrew.david.hill@gridnode.com]
Sent: Tuesday, September 24, 2002 3:02 AM
(Incidentally, using the browsers back button in such a case results in a
rather bad case of server state confusion!)
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [OT][WORKFLOW] Any best practice for "back", "save",
"continu e" buttons?
Posted by Daniel Jaffa <ja...@courtinnovation.org>.
But do you have to worry about people that disable javascript, check to see
if they do and if they do not tell them that they have to enable Javascript
to use your site.
----- Original Message -----
From: "Eddie Bush" <ek...@swbell.net>
To: "Struts Users Mailing List" <st...@jakarta.apache.org>
Sent: Tuesday, September 24, 2002 10:10 AM
Subject: Re: [OT][WORKFLOW] Any best practice for "back", "save", "continu
e" buttons?
> Yes, it does! I can vouch for it! I personally know two (highly
> educated) people that refuse to allow them. They are ignorant about
> them, of course, but that doesn't change the fact that people *do*
> disable cookies/JavaScript!
>
> Now, if I know two people, then how many more people are there "out
> there" that are doing this? Sorry to disagree - I view it as a "fact of
> life". Having said that though, I don't not use JavaScript because of
> it. That's yet another opportunity to control things - it certainly
> does have applicability.
>
> Galbreath, Mark wrote:
>
> >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 [mailto:andrew.david.hill@gridnode.com]
> >Sent: Tuesday, September 24, 2002 3:02 AM
> >
> >(Incidentally, using the browsers back button in such a case results in a
> >rather bad case of server state confusion!)
> >
>
> --
> Eddie Bush
>
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [OT][WORKFLOW] Any best practice for "back", "save", "continu e" buttons?
Posted by Andrew Hill <an...@gridnode.com>.
Id be dead without JS, and I think people would be silly to disable it, but
cookies is another matter. I can understand folk disabling those...
-----Original Message-----
From: Eddie Bush [mailto:ekbush@swbell.net]
Sent: Tuesday, September 24, 2002 22:10
To: Struts Users Mailing List
Subject: Re: [OT][WORKFLOW] Any best practice for "back", "save",
"continu e" buttons?
Yes, it does! I can vouch for it! I personally know two (highly
educated) people that refuse to allow them. They are ignorant about
them, of course, but that doesn't change the fact that people *do*
disable cookies/JavaScript!
Now, if I know two people, then how many more people are there "out
there" that are doing this? Sorry to disagree - I view it as a "fact of
life". Having said that though, I don't not use JavaScript because of
it. That's yet another opportunity to control things - it certainly
does have applicability.
Galbreath, Mark wrote:
>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 [mailto:andrew.david.hill@gridnode.com]
>Sent: Tuesday, September 24, 2002 3:02 AM
>
>(Incidentally, using the browsers back button in such a case results in a
>rather bad case of server state confusion!)
>
--
Eddie Bush
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [OT][WORKFLOW] Any best practice for "back", "save",
"continu e" buttons?
Posted by Eddie Bush <ek...@swbell.net>.
Yes, it does! I can vouch for it! I personally know two (highly
educated) people that refuse to allow them. They are ignorant about
them, of course, but that doesn't change the fact that people *do*
disable cookies/JavaScript!
Now, if I know two people, then how many more people are there "out
there" that are doing this? Sorry to disagree - I view it as a "fact of
life". Having said that though, I don't not use JavaScript because of
it. That's yet another opportunity to control things - it certainly
does have applicability.
Galbreath, Mark wrote:
>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 [mailto:andrew.david.hill@gridnode.com]
>Sent: Tuesday, September 24, 2002 3:02 AM
>
>(Incidentally, using the browsers back button in such a case results in a
>rather bad case of server state confusion!)
>
--
Eddie Bush
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [OT][WORKFLOW] Any best practice for "back", "save", "continue" buttons?
Posted by Andrew Hill <an...@gridnode.com>.
Would your solution work without the cookies (ie: just the JS)? (Im trying
to avoid cookies if I can, though if I cant I wont be too worried).
Any chance you could share your technique?
-----Original Message-----
From: Galbreath, Mark [mailto:Galbreath@tessco.com]
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!
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 [mailto:andrew.david.hill@gridnode.com]
Sent: Tuesday, September 24, 2002 3:02 AM
(Incidentally, using the browsers back button in such a case results in a
rather bad case of server state confusion!)
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>