you don't want to disable buttons after they are clicked

re: you don't want to disable buttons after they are clicked

PH81 — Tue, 15 Sep 2009 13:04:44 GMT

maybe use javascript to change the onclick event of button so that it asks on next click user that u have just send request and ist still beeing prosessed

do u want to resend your request.

if the first request (or any) is ok it will set the onclick to original value that button is ready to click without prompt.

re: you don't want to disable buttons after they are clicked

Arun — Thu, 11 Sep 2008 04:08:51 GMT

codekeep.net/.../9b1d8e28-bd4d-48c7-b64e-f3d7da976dfb.aspx

re: you don't want to disable buttons after they are clicked

ajones — Wed, 03 Sep 2008 19:11:31 GMT

Disabling a button and still getting a postback is easy just use the following code and it works great all of the time:

cmdButton.Attributes.Add("onclick", "this.value='Please wait...';this.disabled=true;" & GetPostBackEventReference(Me.cmdButton))

Viola, you have a disabled button with postback and preventing any duplicates without doing any server side crap. Put this code in the Page_Load event.

re: you don't want to disable buttons after they are clicked

Mal — Fri, 21 Dec 2007 16:51:29 GMT

As a none wokring sample that I have been working on recently I come up with this

</form>

You can hide the reset button and change the color of the submit button at the same time as showing an animated image that the process has started.

re: you don't want to disable buttons after they are clicked

Frank — Fri, 26 Oct 2007 16:10:36 GMT

Just a though. Another way to handle this is to spawn a new thread to handle the functionality that the button is supposed to handle. I know that sounds like a lot of work, but it really isn't.

re: you don't want to disable buttons after they are clicked

Rupesh — Thu, 09 Aug 2007 11:52:26 GMT

I have also faced the same problem but i used floating transparent division for avoiding this issue. All we have to do one simple thing on client click just show division with 100% width and 100% height which covers all the page (position of div u can keep as absolute according to u r setting) and if user clicks again event will fire on that div not on button.i did same thing and my problem is solved anyway if any of u r having better solution plz add here

re: you don't want to disable buttons after they are clicked

John — Sat, 15 May 2004 22:13:00 GMT

I found that disabling the submit button works fine in Mozilla, but not in IE. The work-around was to create an onSubmit event in the form that disabled the submit button.

re: you don't want to disable buttons after they are clicked

TBORE Toronto — Mon, 05 Apr 2004 09:47:00 GMT

I would still handle it on the server with a session variable set when data is accepted from the user. A hidden field variable is sent along as last_post_id or something. A quick check will reveal if the new request is identical to the previous one.

re: you don't want to disable buttons after they are clicked

JulianG — Fri, 05 Mar 2004 20:03:00 GMT

Hey!
What about disabling the button for a while?

Then you enable it again (if the page is still there).

This way if the post fails, the button will be enabled again in a few seconds.

Of course you have no way to know the post failed or it's still posting, but...
what the hell! Maybe it's a good option.

re: you don't want to disable buttons after they are clicked

Larryb — Fri, 23 Jan 2004 13:54:00 GMT

All you need to do is put a layer on it or whatever and remove the layer on a timer, say after 30 seconds.