Sometimes you may encounter a scenario in which the RadButton control doesn’t trigger postback and is rendered as an input HTML element of type button. Most probably this behavior is caused by a validation control on the page, containing the RadButton.
For example you can take the following situation – a page with ASP TextBox and a RequiredFieldValidator, attached to that text box. The page is submitted via RadButton, which has default settings. Below is the markup of the described page:
<asp:TextBox ID="NameInput" runat="server" /> <asp:RequiredFieldValidator ID="RequiredNameValidator" ControlToValidate="NameInput" runat="server" Display="Dynamic" /> <telerik:RadButton RenderMode="Lightweight" ID="btnSubmit" runat="server" Text="Submit"> </telerik:RadButton>
In some cases the validation requirements are not met and the RadButton doesn’t initiate postback, which may cause confusion if the validation is not easy to spot and the button is not supposed to be part of it.
If you want to exclude the RadButton from the validation mechanism of the page, you can set its CausesValidation property to false (this is also valid for a regular Button control).