This is a migrated thread and some comments may be shown as answers.

Problem with DefaultButton in Q1 2012

34 Answers 595 Views

General Discussions

This is a migrated thread and some comments may be shown as answers.

Marian asked on 21 Feb 2012, 12:37 PM

Hi to all,
I have upgraded my telerik controls from 2011.2.915.40 to 2012.1.215.40 with msi installer.
After uprade I discovered that defaultbutton declared for asp:Panel does not fire postback on pressing
the key Enter.
Here is small example. It works fine with older Telerik.Web.UI, but not with Q1 2012.

<%@ Page Language="C#" AutoEventWireup="True" CodeBehind="Default.aspx.cs" Inherits="Test._Default" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">

<head runat="server">

<title>Test</title>

</head>

<body>

<form id="MainForm" runat="server">

<telerik:RadScriptManager ID="RadSCM" runat="server" />

<asp:Panel ID="pnlWrapper" runat="server" DefaultButton="btnSearch">

<telerik:RadTextBox ID="tbSearch" runat="server" EmptyMessage="Search" Width="130" />

<telerik:RadButton ID="btnSearch" ButtonType="StandardButton" Text="Search" ToolTip="Searching" runat="server" OnClick="btnSearch_Click" />

</asp:Panel>

<asp:Label ID="lblMsg" runat="server" />

</form>

</body>

</html>

using System;

namespace Test

{

public partial class _Default : System.Web.UI.Page

{

protected void Page_Load(object sender, EventArgs e)

{

lblMsg.Text = string.Empty;

}

protected void btnSearch_Click(object sender, EventArgs e)

{

lblMsg.Text = "O.K. - Button fired";

}

Does anybody know where is the problem?
Thanks
-Marian

34 Answers, 1 is accepted

answered on 22 Feb 2012, 06:03 PM

Hello,

We are aware of this problem and we are looking for a solution. Currently I am unable to confirm if it would be a fix for the problem or if it will remain as limitation of the new rendering of RadInput. There are several options for fixing the behavior of the RadTextBox control, which could be used for the time being:

You could still use the old rendering by setting the EnableSingleInputRendering property to false for your RadInputs.
You could set AutoPostBack to true for your Input if it is applicable in your scenario.
You could utilize the client-side event OnKeyPress in order to check if the pressed keyboard button is Enter and if it is, to click the RadButton programmatically (via its client-side method click()).

Additionally you can check this forum thread.

Feel free to let us know if you run into more difficulties.

All the best,
Slav
the Telerik team

If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.

answered on 22 Feb 2012, 07:13 PM

I can't believe I was just read. I really really hope it will not "remain as a limitation of the new rendering of RadInput".

Do you realistically believe we will going to hunt down all the textboxes in our apps to add that property? And even if we do, what about the comboboxes, which do not expose it?

I am using validators and validation summary. User presses enter and I show him what and where to enter. Until last update everything worked smoothly, users were happy and I was happy too. Now they aren't happy anymore and guess what's my mood.

Please put the defaultbutton back. I don't understand why such a breaking change, which make no sense anyway. Why choose a implementation which breaks a well established one?

Besides that, if I press enter in a textbox on a form that has the DefaultButton property set, then the entire page stops working. Tab doesn't navigate to next control anymore, the browers eats 60-90% of the processor and the red upper right x cannot be clicked (all the processing goes to some javascript in the page).

Guys, please FIX this. No "will remain as a limitation". Limitation doesn't mean "we broke it".

answered on 28 Feb 2012, 08:16 PM

I am getting "Telerik is undefined" javascript error. I have unzipped the hotfix overwriting the old folder structure, then upgraded the website using Upgrade Wizard. Is there anything else I should do? (deleted the framework cache and visual studio cache).

The error occurs here:

WebForm_AutoFocus('frmMain_ctlLogin');Sys.Application.add_init(function() {

$create(Telerik.Web.UI.RadAjaxManager, {"_updatePanels":"","ajaxSettings":[],"clientEvents":{OnRequestStart:"",OnResponseEnd:""},"defaultLoadingPanelID":"","enableAJAX":true,"enableHistory":false,"links":[],"styles":[],"uniqueID":"ctl00$myRadAjaxManager","updatePanelsRenderMode":0}, null, null, $get("ctl00_myRadAjaxManager"));

The error occurs on a brand new website as well. What can i do to fix this?

answered on 01 Mar 2012, 10:36 AM

Unistalled Q1 2012, installed it back, upgraded the dll in the bin folder and now it doesn't hang anymore, but still needs work.

Create a blank new RadControls webpage. Drop an <asp:login> cotnrol on it and run the thing. Click the login button - it will show asterisks next to both textboxes.

Run the webpage again, set focus in first textbox and press enter. It will show an asterisk next to that text box, and not to second one. That means user need to tab to next textbox and press enter, then tab to next one, press enter and so on, in order to get all the validation messages.

I am rollling back to Q3 2011, and most probably this is my last ASP.NET project built with Telerik controls.

Have a good day.

answered on 05 Mar 2012, 05:59 PM

Marian -- I have also noticed issues with width. I have a simple log on page with 3 text boxes. All are set to an absolute width of 200px yet the password TextBox with the property TextMode="Password" is noticeably shorter than the TextBoxes without setting the TextMode property.

Luckily on the log on page I really do not need to use the RadControls so I was able to revert back to the normal ASP TextBox to fix the width problem as well as the DefaultButton problem. No so lucky on the other pages however and am eagerly waiting for the official service release so I can deploy my application. Until then I will stick with the previous version.

Product Bundles

DevCraft

Web

Mobile

Document Management

Desktop

Reporting & Mocking

Automated Testing

CMS

UI/UX Tools

Debugging

Free Tools

Support and Learning

Productivity and Design Tools

Problem with DefaultButton in Q1 2012

34 Answers, 1 is accepted