blocks|key|1751543|text|禁用提交处理程序末尾的按钮。如果验证失败，它应该在此之前返回false。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1751544|但是，JavaScript方法并不可靠，因此您还应该有一些东西来检测服务器上的重复项。|1751545|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Disable the button at the very end of your submit handler. If the validation fails, it should return false before that.

However, the JavaScript approach is not something that can be relied upon, so you should have something to detect duplicates on the server as well.

blocks|key|1751596|text|不确定这是否会有帮助，但是表单中有onsubmit事件。每当表单提交(从任何按钮或控件)时，都可以使用此事件。参考：http://www.htmlcodetutorial.com/forms/_FORM_onSubmit.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1751597|entityMap|0|LINK|mutability|MUTABLE|url|http://www.htmlcodetutorial.com/forms/_FORM_onSubmit.html^0|1M|1L|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Not sure if this will help, but there's onsubmit event in form. You can use this event whenever the form submit (from any button or controls).
For reference: <a href="http://www.htmlcodetutorial.com/forms/_FORM_onSubmit.html" rel="nofollow noreferrer">http://www.htmlcodetutorial.com/forms/_FORM_onSubmit.html</a>

blocks|key|1536677|text|以下功能在不需要禁用部件的情况下非常有用，因为禁用部件往往不可靠。只需使用"return+check_submit();“作为提交按钮的onclick处理程序的一部分。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1536678|还应该有一个隐藏字段来保存form_submitted初始值0；|1536679|<input+type="hidden"+name="form_submitted"+value="0">

function+check_submit+(){
++++++++++++if+(document.Form1.form_submitted.value+==+1){
++++++++++++++++alert("Don't+submit+twice.+Please+wait.");
++++++++++++++++return+false;
++++++++++++}
++++++++++++else{
++++++++++++++++document.Form1.form_submitted.value+=+1;
++++++++++++++++return+true;
++++++++++++}
++++++++++++return+false;
++++}|code-block|syntax|javascript|1536680|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

The following function is useful without needing the disabling part which tends to be unreliable. Just use "return check_submit();" as part of the onclick handler of the submit buttons.

There should also be a hidden field to hold the form_submitted initial value of 0;

<pre><code>&lt;input type="hidden" name="form_submitted" value="0"&gt;

function check_submit (){
 if (document.Form1.form_submitted.value == 1){
 alert("Don't submit twice. Please wait.");
 return false;
 }
 else{
 document.Form1.form_submitted.value = 1;
 return true;
 }
 return false;
 }
</code></pre>

blocks|key|1751727|text|一种解决方案是在单击按钮时设置一个隐藏字段，其数字为1。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1751728|在按钮点击处理程序中，第一件事是检查这个数字，如果它不是1，就从函数中返回。|1751729|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

A solution will be to set a hidden field when the button is clicked, with the number 1. 

On the button click handler first thing is to check that number if it is something other than 1 just return out of the function.

blocks|key|1751786|text|您还可以利用表单上可用的onsubmit()+javascript事件。此事件在表单实际提交时触发，并且在验证完成之前不应捕获。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1751787|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You may also be able to take advantage of the onsubmit() javascript event that is available on forms. This event fires when the form is actually submit and shouldn't trap until after the validation is complete.

blocks|key|1536838|text|试一试：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1536839|using+System;
using+System.Collections.Generic;
using+System.Linq;
using+System.Web;
using+System.Web.UI;
using+System.Web.UI.WebControls;
using+System.Threading;

public+partial+class+_Default+:+System.Web.UI.Page+
{
++++protected+void+Page_Load(object+sender,+EventArgs+e)
++++{

+++++++++//+Identify+button+as+a+"disabled-when-clicked"+button...
+++++++++WebHelpers.DisableButtonOnClick(+buttonTest,+"showPleaseWait"+);+
++++}

++++protected+void+buttonTest_Click(+object+sender,+EventArgs+e+)
++++{
++++++++//+Emulate+a+server-side+process+to+demo+the+disabled+button+during
++++++++//+postback.
++++++++Thread.Sleep(+5000+);
++++}
}



using+System;
using+System.Web;
using+System.Web.UI.WebControls;
using+System.Text;

public+class+WebHelpers
{
++++//
++++//+Disable+button+with+no+secondary+JavaScript+function+call.
++++//
++++public+static+void+DisableButtonOnClick(+Button+ButtonControl+)
++++{
++++++++DisableButtonOnClick(+ButtonControl,+string.Empty+);++++
++++}

++++//
++++//+Disable+button+with+a+JavaScript+function+call.
++++//
++++public+static+void+DisableButtonOnClick(+Button+ButtonControl,+string+ClientFunction+)
++++{+++
++++++++StringBuilder+sb+=+new+StringBuilder(+128+);

++++++++//+If+the+page+has+ASP.NET+validators+on+it,+this+code+ensures+the
++++++++//+page+validates+before+continuing.
++++++++sb.Append(+"if+(+typeof(+Page_ClientValidate+)+==+'function'+)+{+"+);
++++++++sb.Append(+"if+(+!+Page_ClientValidate()+)+{+return+false;+}+}+"+);

++++++++//+Disable+this+button.
++++++++sb.Append(+"this.disabled+=+true;"+);+

++++++++//+If+a+secondary+JavaScript+function+has+been+provided,+and+if+it+can+be+found,
++++++++//+call+it.+Note+the+name+of+the+JavaScript+function+to+call+should+be+passed+without
++++++++//+parens.
++++++++if+(+!+String.IsNullOrEmpty(+ClientFunction+)+)+
++++++++{
++++++++++++sb.AppendFormat(+"if+(+typeof(+{0}+)+==+'function'+)+{{+{0}()+}};",+ClientFunction+);++
++++++++}

++++++++//+GetPostBackEventReference()+obtains+a+reference+to+a+client-side+script+function+
++++++++//+that+causes+the+server+to+post+back+to+the+page+(ie+this+causes+the+server-side+part+
++++++++//+of+the+"click"+to+be+performed).
++++++++sb.Append(+ButtonControl.Page.ClientScript.GetPostBackEventReference(+ButtonControl+)+%2B+";"+);

++++++++//+Add+the+JavaScript+created+a+code+to+be+executed+when+the+button+is+clicked.
++++++++ButtonControl.Attributes.Add(+"onclick",+sb.ToString()+);
++++}
}|code-block|syntax|javascript|1536840|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Give this a whirl:

<pre><code>using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Threading;

public partial class _Default : System.Web.UI.Page 
{
 protected void Page_Load(object sender, EventArgs e)
 {

 // Identify button as a "disabled-when-clicked" button...
 WebHelpers.DisableButtonOnClick( buttonTest, "showPleaseWait" ); 
 }

 protected void buttonTest_Click( object sender, EventArgs e )
 {
 // Emulate a server-side process to demo the disabled button during
 // postback.
 Thread.Sleep( 5000 );
 }
}



using System;
using System.Web;
using System.Web.UI.WebControls;
using System.Text;

public class WebHelpers
{
 //
 // Disable button with no secondary JavaScript function call.
 //
 public static void DisableButtonOnClick( Button ButtonControl )
 {
 DisableButtonOnClick( ButtonControl, string.Empty ); 
 }

 //
 // Disable button with a JavaScript function call.
 //
 public static void DisableButtonOnClick( Button ButtonControl, string ClientFunction )
 { 
 StringBuilder sb = new StringBuilder( 128 );

 // If the page has ASP.NET validators on it, this code ensures the
 // page validates before continuing.
 sb.Append( "if ( typeof( Page_ClientValidate ) == 'function' ) { " );
 sb.Append( "if ( ! Page_ClientValidate() ) { return false; } } " );

 // Disable this button.
 sb.Append( "this.disabled = true;" ); 

 // If a secondary JavaScript function has been provided, and if it can be found,
 // call it. Note the name of the JavaScript function to call should be passed without
 // parens.
 if ( ! String.IsNullOrEmpty( ClientFunction ) ) 
 {
 sb.AppendFormat( "if ( typeof( {0} ) == 'function' ) {{ {0}() }};", ClientFunction ); 
 }

 // GetPostBackEventReference() obtains a reference to a client-side script function 
 // that causes the server to post back to the page (ie this causes the server-side part 
 // of the "click" to be performed).
 sb.Append( ButtonControl.Page.ClientScript.GetPostBackEventReference( ButtonControl ) + ";" );

 // Add the JavaScript created a code to be executed when the button is clicked.
 ButtonControl.Attributes.Add( "onclick", sb.ToString() );
 }
}
</code></pre>

blocks|key|1751853|text|如果验证成功，则禁用该按钮。如果不是，那就不要。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1751854|function+validate(form)+{
++//+perform+validation+here
++if+(isValid)+{
++++form.mySubmitButton.disabled+=+true;
++++return+true;
++}+else+{
++++return+false;
++}
}

<form+onsubmit="return+validate(this);">...</form>|code-block|syntax|javascript|1751855|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

if the validation is successful, then disable the button. if it's not, then don't.

<pre><code>function validate(form) {
 // perform validation here
 if (isValid) {
 form.mySubmitButton.disabled = true;
 return true;
 } else {
 return false;
 }
}

&lt;form onsubmit="return validate(this);"&gt;...&lt;/form&gt;
</code></pre>

blocks|key|1536942|text|这是一种比rp建议的更简单但相似的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1536943|function+submit(button)+{
++++++++Page_ClientValidate();+
++++++++if(Page_IsValid)
++++++++{
++++++++++++button.disabled+=+true;
++++++++}
}

+<asp:Button+runat="server"+ID="btnSubmit"+OnClick="btnSubmit_OnClick"+OnClientClick="submit(this)"+Text="Submit+Me"+/>|code-block|syntax|javascript|1536944|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/106509/disable-button-on-form-submission#106958^0|5|2|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

This is an easier but similar method than what <a href="https://stackoverflow.com/questions/106509/disable-button-on-form-submission#106958">rp</a> has suggested:

<pre><code>function submit(button) {
 Page_ClientValidate(); 
 if(Page_IsValid)
 {
 button.disabled = true;
 }
}

 &lt;asp:Button runat="server" ID="btnSubmit" OnClick="btnSubmit_OnClick" OnClientClick="submit(this)" Text="Submit Me" /&gt;
</code></pre>

blocks|key|1537006|text|将按钮上的可见性设置为“无”；|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1537007|btnSubmit.Attributes("onClick")+=+document.getElementById('btnName').style.display+=+'none';|code-block|syntax|javascript|1537008|它不仅可以防止双重提交，而且对用户来说，它是一个明确的指示器，表明您不希望按钮按下多次。|1537009|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Set the visibility on the button to 'none';

<pre><code>
btnSubmit.Attributes("onClick") = document.getElementById('btnName').style.display = 'none';</code></pre>

Not only does it prevent the double submission, but it is a clear indicator to the user that you don't want the button pressed more than once.

blocks|key|1537045|text|我不是一个非常喜欢在代码隐藏中编写所有javascript的人。这是我的最终解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1537046|按钮：|1537047|<asp:Button+ID="btnSubmit"+runat="server"+Text="Submit"+OnClick="btnSubmit_Click"+OnClientClick="doSubmit(this)"+/>|code-block|syntax|javascript|1537048|Javascript：|1537049|<script+type="text/javascript">
</script>|1537050|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I'm not a huge fan of writing all that javascript in the code-behind. Here is what my final solution looks like.

Button:

<pre><code>&lt;asp:Button ID="btnSubmit" runat="server" Text="Submit" OnClick="btnSubmit_Click" OnClientClick="doSubmit(this)" /&gt;
</code></pre>

Javascript:

<pre><code>&lt;script type="text/javascript"&gt;&lt;!--
function doSubmit(btnSubmit) {
 if (typeof(Page_ClientValidate) == 'function' &amp;&amp; Page_ClientValidate() == false) { 
 return false;
 } 
 btnSubmit.disabled = 'disabled';
 btnSubmit.value = 'Processing. This may take several minutes...';
 &lt;%= ClientScript.GetPostBackEventReference(btnSubmit, string.Empty) %&gt;; 
}
//--&gt;
&lt;/script&gt;
</code></pre>

blocks|key|1537100|text|我刚听说过的"DisableOnSubmit“属性，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1537101|<asp:Button+ID="submit"+runat="server"+Text="Save"
++++OnClick="yourClickEvent"+DisableOnSubmit="true"+/>|code-block|syntax|javascript|1537102|渲染时，按钮的onclick属性如下所示：|1537103|onclick="this.disabled=true;+setTimeout('enableBack()',+3000);
++WebForm_DoPostBackWithOptions(new
++WebForm_PostBackOptions('yourControlsName',+'',+true,+'',+'',+false,+true))|1537104|“enableBack()”javascript函数看起来像这样：|1537105|function+enableBack()
{
++++document.getElementById('yourControlsName').disabled=false;
}|1537106|因此，当按钮被单击时，它将被禁用3秒。如果表单成功发布，则您永远不会看到该按钮重新启用。但是，如果任何验证器失败，则该按钮将在3秒后再次启用。|1537107|所有这一切只需在按钮上设置一个属性--不需要手动编写任何javascript代码。|1537108|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

Just heard about the "DisableOnSubmit" property of an &lt;asp:Button&gt;, like so:

<pre><code>&lt;asp:Button ID="submit" runat="server" Text="Save"
 OnClick="yourClickEvent" DisableOnSubmit="true" /&gt;
</code></pre>

When rendered, the button's onclick attribute looks like so:

<pre><code>onclick="this.disabled=true; setTimeout('enableBack()', 3000);
 WebForm_DoPostBackWithOptions(new
 WebForm_PostBackOptions('yourControlsName', '', true, '', '', false, true))
</code></pre>

And the "enableBack()' javascript function looks like this:

<pre><code>function enableBack()
{
 document.getElementById('yourControlsName').disabled=false;
}
</code></pre>

So when the button is clicked, it becomes disabled for 3 seconds. If the form posts successfully then you never see the button re-enable. If, however, any validators fail then the button becomes enabled again after 3 seconds.

All this just by setting an attribute on the button--no javascript code needs to be written by hand.

blocks|key|1752098|text|请注意，如果您在UseSubmitBehavior="false"中使用按钮，rp的方法将重复提交您的表单。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1752099|我使用以下rp代码的变体：|1752100|public+static+void+DisableButtonOnClick(Button+button,+string+clientFunction)
{
++++//+If+the+page+has+ASP.NET+validators+on+it,+this+code+ensures+the
++++//+page+validates+before+continuing.
++++string+script+=+"if+(typeof(Page_ClientValidate)+==+'function')+{+"
++++++++++++%2B+"if+(!Page_ClientValidate())+{+return+false;+}+}+";

++++//+disable+the+button
++++script+%2B=+"this.disabled+=+true;+";

++++//+If+a+secondary+JavaScript+function+has+been+provided,+and+if+it+can+be+found,+call+it.
++++//+Note+the+name+of+the+JavaScript+function+to+call+should+be+passed+without+parens.
++++if+(!string.IsNullOrEmpty(clientFunction))
++++++++script+%2B=+string.Format("if+(typeof({0})+==+'function')+{{+{0}()+}}+",+clientFunction);

++++//+only+need+to+post+back+if+button+is+using+submit+behaviour
++++if+(button.UseSubmitBehavior)
++++++++script+%2B=+button.Page.GetPostBackEventReference(button)+%2B+";+";

++++button.Attributes.Add("onclick",+script);
}|code-block|syntax|javascript|1752101|entityMap^0|8|P|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|S|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

Note that rp's approach will double submit your form if you are using buttons with <code>UseSubmitBehavior="false"</code>.

I use the following variation of rp's code:

<pre><code>public static void DisableButtonOnClick(Button button, string clientFunction)
{
 // If the page has ASP.NET validators on it, this code ensures the
 // page validates before continuing.
 string script = "if (typeof(Page_ClientValidate) == 'function') { "
 + "if (!Page_ClientValidate()) { return false; } } ";

 // disable the button
 script += "this.disabled = true; ";

 // If a secondary JavaScript function has been provided, and if it can be found, call it.
 // Note the name of the JavaScript function to call should be passed without parens.
 if (!string.IsNullOrEmpty(clientFunction))
 script += string.Format("if (typeof({0}) == 'function') {{ {0}() }} ", clientFunction);

 // only need to post back if button is using submit behaviour
 if (button.UseSubmitBehavior)
 script += button.Page.GetPostBackEventReference(button) + "; ";

 button.Attributes.Add("onclick", script);
}
</code></pre>

blocks|key|1752198|text|正确的方法(至少就用户友好性而言)是使用OnClientClick属性禁用按钮，执行客户端验证，然后使用验证结果继续或重新启用按钮。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1752199|当然，您还应该为此编写服务器端代码，因为您不能依赖于由于缺少或特定的JavaScript实现而执行的验证。但是，如果您依赖于服务器来控制按钮的启用/禁用状态，那么您基本上无法阻止用户多次提交表单。因此，您应该有某种逻辑来检测同一用户在短时间内提交的多个内容(例如，来自同一会话的相同值)。|1752200|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The correct (as far as user-friendliness is concerned, at least) way would be to disable the button using the OnClientClick attribute, perform the client-side validation, and then use the result of that to continue or re-enable the button.

Of course, you should ALSO write server-side code for this, as you cannot rely on the validation even being carried out due to a lack, or particular implementation, of JavaScript. However, if you rely on the server controlling the button's enabled / disabled state, then you basically have no way of blocking the user submitting the form multiple times anyway. For this reason you should have some kind of logic to detect multiple submissions from the same user in a short time period (identical values from the same Session, for example).

blocks|key|1537292|text|我的一个解决方案如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1537293|将脚本添加到aspx文件的page_load中|1537294|++++HtmlGenericControl+includeMyJava+=+new+HtmlGenericControl("script");
++++includeMyJava.Attributes.Add("type",+"text/javascript");
++++includeMyJava.InnerHtml+=+"\nfunction+dsbButton(button)+{";
++++includeMyJava.InnerHtml+%2B=+"\nPage_ClientValidate();";
++++includeMyJava.InnerHtml+%2B=+"\nif(Page_IsValid)";
++++includeMyJava.InnerHtml+%2B=+"\n{";
++++includeMyJava.InnerHtml+%2B=+"\nbutton.disabled+=+true;";
++++includeMyJava.InnerHtml+%2B=+"}";
++++includeMyJava.InnerHtml+%2B=+"\n}";
++++this.Page.Header.Controls.Add(includeMyJava);|code-block|syntax|javascript|1537295|然后设置aspx按钮参数，如下所示：|1537296|<asp:Button+ID="send"+runat="server"+UseSubmitBehavior="false"+OnClientClick="dsbButton(this);"+Text="Send"+OnClick="send_Click"+/>|1537297|请注意，"onClientClick“有助于禁用”to“按钮，"UseSubmitBehaviour”禁用页面的传统提交行为，并允许asp.net根据用户脚本呈现提交行为。|1537298|祝好运|1537299|-Waqas+Aslam|1537300|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

one of my solution is as follow:

add the script in the page_load of your aspx file

<pre><code> HtmlGenericControl includeMyJava = new HtmlGenericControl("script");
 includeMyJava.Attributes.Add("type", "text/javascript");
 includeMyJava.InnerHtml = "\nfunction dsbButton(button) {";
 includeMyJava.InnerHtml += "\nPage_ClientValidate();";
 includeMyJava.InnerHtml += "\nif(Page_IsValid)";
 includeMyJava.InnerHtml += "\n{";
 includeMyJava.InnerHtml += "\nbutton.disabled = true;";
 includeMyJava.InnerHtml += "}";
 includeMyJava.InnerHtml += "\n}";
 this.Page.Header.Controls.Add(includeMyJava);
</code></pre>

and then set your aspx button parameters as follow:

<pre><code>&lt;asp:Button ID="send" runat="server" UseSubmitBehavior="false" OnClientClick="dsbButton(this);" Text="Send" OnClick="send_Click" /&gt;
</code></pre>

Note that "onClientClick" helps to disable to button and "UseSubmitBehaviour" disables the traditional submitting behaviour of page and allows asp.net to render the submit behaviour upon user script.

good luck

-Waqas Aslam

blocks|key|1752279|text|因此，通过javascript简单地禁用按钮并不是一个跨浏览器兼容的选项。如果您只使用OnClientClick="this.disabled=true;"，Chrome将不会提交表单|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1752280|以下是我在Firefox+9、Internet+Explorer+9和Chrome+16上测试过的解决方案：|1752281|<script+type="text/javascript">
var+buttonToDisable;
function+disableButton(sender)
{
++++buttonToDisable=sender;
++++setTimeout('if(Page_IsValid==true)buttonToDisable.disabled=true;',+10);
}
</script>|code-block|syntax|javascript|1752282|然后使用表单提交按钮的单击事件注册'disableButton‘，一种方法是：|1752283|<asp:Button+runat="server"+ID="btnSubmit"+Text="Submit"+OnClientClick="disableButton(this);"+/>|1752284|值得注意的是，如果客户端验证失败，这就解决了按钮被禁用的问题。也不需要服务器端处理。|1752285|entityMap^0|17|Z|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|11|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|T|$]]

So simply disabling the button via javascript is not a cross-browser compatible option. Chrome will not submit the form if you just use <code>OnClientClick="this.disabled=true;"</code> 
Below is a solution that I have tested in Firefox 9, Internet Explorer 9, and Chrome 16:

<pre><code>&lt;script type="text/javascript"&gt;
var buttonToDisable;
function disableButton(sender)
{
 buttonToDisable=sender;
 setTimeout('if(Page_IsValid==true)buttonToDisable.disabled=true;', 10);
}
&lt;/script&gt;
</code></pre>

Then register 'disableButton' with the click event of your form submission button, one way being:

<pre><code>&lt;asp:Button runat="server" ID="btnSubmit" Text="Submit" OnClientClick="disableButton(this);" /&gt;
</code></pre>

Worth noting that this gets around your issue of the button being disabled if client side validation fails. Also requires no server side processing.

blocks|key|1537373|text|基于@rp的回答，我对其进行了修改，以调用自定义函数，并在成功时提交并禁用或在错误时使用"halt“：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1537374|public+static+void+DisableButtonOnClick(Button+ButtonControl,+string+ClientFunction)
{
++++StringBuilder+sb+=+new+StringBuilder(128);

++++if+(!String.IsNullOrEmpty(ClientFunction))
++++{
++++++++sb.AppendFormat("if+(typeof({0})+==+'function')+{{+if+({0}())+{{+{1};+this.disabled=true;+return+true;+}}+else+{{+return+false;+}}+}};",+ClientFunction,+ButtonControl.Page.ClientScript.GetPostBackEventReference(ButtonControl,+null));
++++}
++++else
++++{
++++++++sb.Append("return+true;");
++++}

++++ButtonControl.Attributes.Add("onclick",+sb.ToString());
}|code-block|syntax|javascript|1537375|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Building on @rp.'s answer, I modified it to invoke the custom function and either submit and disable on success or "halt" on error:

<pre><code>public static void DisableButtonOnClick(Button ButtonControl, string ClientFunction)
{
 StringBuilder sb = new StringBuilder(128);

 if (!String.IsNullOrEmpty(ClientFunction))
 {
 sb.AppendFormat("if (typeof({0}) == 'function') {{ if ({0}()) {{ {1}; this.disabled=true; return true; }} else {{ return false; }} }};", ClientFunction, ButtonControl.Page.ClientScript.GetPostBackEventReference(ButtonControl, null));
 }
 else
 {
 sb.Append("return true;");
 }

 ButtonControl.Attributes.Add("onclick", sb.ToString());
}
</code></pre>

blocks|key|1537466|text|在我们的一个遗留应用程序中遇到了rp的代码，该应用程序正在与一些疯狂的行为作斗争。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1537467|我发现了一种奇怪的事件触发组合--当DisableButtonOnClick()在UpdatePanel中的asp按钮上使用时，POST将被发送两次(一次由DisableButtonOnClick()添加的doPostBack发送，一次由UpdatePanel发送)。然而，这只发生在一些浏览器上(早期版本的Edge，但不是最近的版本，IE11做到了这一点，Chrome和FireFox没有做到这一点(至少在我测试的版本中是这样))。我认为Chrome和更新版本的Edge正在以某种方式在内部处理这种情况。在IE中跟踪F12开发工具的问题-两个帖子发生得如此接近，以至于第一个帖子立即中止，但在某些情况下(网络延迟，用户机器负载等)，在浏览器中止之前，请求确实会到达服务器。因此，这导致了一个看似随机的双post来自整个系统的按钮按下，这是一个痛苦的追查。修复方法是在doPostBack后面添加一个"return+false;“，以防止UpdatePanel在旧浏览器运行时介入。|1537468|TLDR+-注意updatepanel中按钮上的代码。这是一个很好的方法和很好的方法，但在我(可能是边缘)的情况下有一个潜在的问题。|1537469|ps+-我会对rp的帖子发表评论，但我没有代表。我想这对未来的旅行者可能会有用。|1537470|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Came across rp's code in a legacy app of ours which was struggling with some crazy behaviour. 

Tracked it down to a strange combination of event firing - when DisableButtonOnClick() was being used on an asp button inside an UpdatePanel, the POST would be sent twice (once by the doPostBack added by DisableButtonOnClick(), and once by the UpdatePanel). However, this only happened with some browsers (early versions of Edge, but not recent ones, and IE11 did this, Chrome and FireFox did not (at least the versions I tested with)). I presume Chrome and newer versions of Edge are dealing with this scenario internally in some way. Tracking the issue with F12 devtools in IE - the two POSTs happen so closely together that the first one gets immediately ABORTED, but under some conditions (network latency, user machine load, etc) the request does get through to the server before the browser can abort. So this results in a seemingly random double-post coming from button presses throughout the system, and it was a pain to trace back. The fix is to add a "return false;" after the doPostBack to prevent the UpdatePanel from getting involved when older browsers are in play.

TLDR - beware of this code on buttons in updatepanels. It's a good approach and nice method but has a potential issue in my (likely edge) case.

ps - I would have commented on rp's post but I don't have the rep. Thought it might be useful for future travelers.

I have a button that I would like to disable when the form submits to prevent the user submitting multiple times.

I have tried naively disabling the button with javascript onclick but then if a client side validation that fails the button remains disabled.

How do I disable the button when the form successfully submits not just when the user clicks?

This is an ASP.NET form so I would like to hook in nicely with the asp.net ajax page lifecycle if possible.

Disable button on form submission

我有一个按钮，我想在表单提交时禁用它，以防止用户多次提交。我曾经尝试过使用javascript onclick禁用该按钮，但是如果客户端验证失败，该按钮仍然处于禁用状态。当表单成功提交时，而不仅仅是用户单击时，如何禁用按钮？这是一个ASP.NET表单，所以如果可能的话，我想很好地与asp.net ajax页面生命周期挂...

问表单提交时禁用按钮
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问表单提交时禁用按钮EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问表单提交时禁用按钮
EN