Radbutton set singleclick UI enable using javascript

[sadesh]

I have used radbutton with  singleclick= true after clicking the button i have set the single click enabled using javascript , then the button is enabled but the UI of button shows as disabled when  autopostback=false . This is not working in telerik verision Q1 2016.

 

<telerik:RadButton ID="singleclickbtn" runat="server" Text="SingleClick" ClientIDMode="Static" SingleClick="true" AutoPostBack="false" OnClientClicked="Click_OnClientClicked"></telerik:RadButton>

 function Click_OnClientClicked(sender, eventArgs) {
                   $find("singleclickbtn").enableAfterSingleClick();
                }

[Danail Vasilev]

Hi Sadesh,

This is an issue with the control, that has already been logged here - http://feedback.telerik.com/Project/108/Feedback/Details/182333, so that you can comment and track its progress. I have also raised the priority of the item.

Regards,
Danail Vasilev
Telerik

[Lax]

Hi Danail,

We have the same issue even after installing Q1 2016 SP1 version of Telerik UI for ASP.NET AJAX? Can you please point out if we are missing anything else?

Looking forward for your response. Thanks,

Lax

[Danail Vasilev]

Hi Lax,

I wasn't able to reproduce the mentioned issue with Q1 2016 SP1. You can watch the following short video test and then tell me if I am missing something - http://screencast.com/t/DX8ec0WbW1rJ

The code I have used for the testing is as follows:

ASPX:

<telerik:RadButton ID="RadButton1" runat="server" AutoPostBack="false"
    Text="New Line"
    SingleClick="true" SingleClickText="processing..">
</telerik:RadButton>
<input type="button" name="name" value="enableAfterSingleClick" onclick="$find('RadButton1').enableAfterSingleClick(); return false;" />

Can you ensure you have properly upgraded the controls? See details about the upgrading process here - http://www.telerik.com/blogs/upgrade-the-version-of-your-telerik-asp.net-controls-in-6-easy-steps

Regards,
Danail Vasilev
Telerik

[Augie]

You all may want to look at RadPushButton as well.  I was experiencing this same issue (I am using 2016 Q1 SP1) described in this post.  I switched it to a RadButton from RadPushButton and the issue was resolved.