Eddie Bush wrote the following on 4/12/2005 12:42 AM:
I personally handle this by having a javascript variable called
"isCancelled" which I initialize to false. The onclick handler for my
cancel button sets it to true. In my validation JavaScript, I check
for this value first thing off the bat.
W
While that might be a good suggestion, it doesn't breech the topic of
how to get the form to submit even when the user selects cancel.
I personally handle this by having a javascript variable called
"isCancelled" which I initialize to false. The onclick handler for my
cancel button sets it to tru
For long running actions, I always prefer to use transaction tokens
(built into Struts) and a processing/wait page. This keeps users busy
watching instead of wondering why the page hasn't changed.
--Kevin
-Original Message-
From: Derrick Koes [mailto:[EMAIL PROTECTED]
Sent: Monday, Ap
seems that the browser stops the form from being able to do ANYTHING with
it...
one solution, but it seems dirty to me, is to add another form with only a
cancel button...
kr,
guenther
--
Günther Wieser
creative-it
Guglgasse 6/1/11/1
A-1110 Wien
Austria
http://www.creative-it.com
-Origin
Rather than try to handle all of this on the client side with
javascript, it might be better and easier to just use the Token approach
to handle duplicate submits. I believe there was an email just today
about this. You can disable the button but the user can still just hit
enter again and you'
5 matches
Mail list logo
