I've tried this, and it works for me:
<asp:TextBox runat="server" ID="txtSearch" OnTextChanged="txtSearch_TextChanged"></asp:TextBox>
<input type="button" value="submit" onclick="<%= GetOnChangedScript() %>" />
The server side asp:TextBox
, and the client side input
which fires __doPostBack
on click. The __doPostBack
script is generated through PostBackOptions
:
protected string GetOnChangedScript()
{
var options = new PostBackOptions(txtSearch, string.Empty);
options.AutoPostBack = true;
options.RequiresJavaScriptProtocol = true;
var script = Page.ClientScript.GetPostBackEventReference(options);
return script;
}
The txtSearch_TextChanged
event handler fires when the value of text box is changed, and the submit
button is clicked.
But note, for controls like TextBox
the text is stored in the viewstate; the new text entered by the user stores in the form data. When the TextBox
load the viewstate data, it gets the old value. This is compared with the new value that comes in the form. If the values are different, the TextChanged
event is fired. If no, the event handler won't be fired. This is the reason for the Page_Load
event get fired (postback occured), but txtSearch_TextChanged
didn't fire due to the value of the TextBox
didn't change.