[Solved] Q1 2009 RadTextBox (and NumericTextBox) shorter by 3px

[Steve Y]

A rad textbox input area is 3px shorter than the width="nnnpx" declaration. This occurs in Q1 2009 release. The Q3 2008 version is fine.

<Telerik:RadNTextBox ID="TextBox3" runat="server" Width="100px" Skin="Office2007" />

This has an input of size 97px. Here's the generated html.

<input id="ctl00_mainPlace_TextBox3_text" class="riTextBox riEnabled" type="text" style="width: 97px;" name="ctl00_mainPlace_TextBox3_text" size="20"/>

Regards,
Steve

[Dimo]

Hi Steve,

In Q1 2009 the RadInput textboxes width is different from the one that you have specified, so that the total width of the control (including borders and paddings) is equal to the specified width. In previous versions, the textboxes were actually wider than specified.

Regards,
Dimo
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

[Steve Y]

Hi Dimo.

I'm all for consistency as long as everything is consistent.

With this change, I now have 3 sizes of text boxes to contend with. I've created a small sample application. For each textbox I made the size="100px". I have a standard asp textbox, a standard asp textbox modified with RadInputManager and a RadTextBox

(sizes specified as: border, padding, box size, padding, border)

asp:textbox = 1, 2, 100, 2, 1 - total 106px
asp:textbox with radinputmanager = 1, 1, 100, 0, 1 - total 104px
radtextbox = 1, 1, 97, 0, 1 - total 100px

I can understand why the radcontrol textboxes are different from an asp textbox. But I don't see why a change would be made to a radtextbox and not to a radinputmanager textbox.

Please. I would like to see a consistency in the rad controls. Either make the radtextbox the same as the input manager (as it was) or make the change across your controls so that an input manager control is the same as the radtextbox.

In my real application I have hundreds of textboxes. I use a combination of radinputmanager and radtextboxes. I would like them to be the same size if I specify a size. Now I am faced with making changes to my application and having to account for a difference of 4px. I started using radinputmanager because of the performance gains I got vs. using radtextboxes. Surely I should not have to change text box size when I flip between the two types of telerik input control.

Thanks, Steve

    <telerik:RadScriptManager ID="RadScriptManager1" runat="server">
        <Scripts>
            <asp:ScriptReference Assembly="Telerik.Web.UI" Name="Telerik.Web.UI.Common.Core.js" />
            <asp:ScriptReference Assembly="Telerik.Web.UI" Name="Telerik.Web.UI.Common.jQuery.js" />
        </Scripts>
    </telerik:RadScriptManager>
    <telerik:RadAjaxManager ID="RadAjaxManager1" runat="server">
    </telerik:RadAjaxManager>
    <telerik:RadStyleSheetManager id="RadStyleSheetManager1" runat="server" />
    <div>
        <br /><telerik:RadTextBox ID="RadTextBox1" Width="100px" runat="server"></telerik:RadTextBox>
        <br /><asp:TextBox ID="TextBox1" Width="100px" runat="server"></asp:TextBox>
        <br /><asp:TextBox ID="TextBox2" Width="100px" runat="server"></asp:TextBox>
    </div>

    <telerik:RadInputManager ID="RadInputManager1" runat="server">
    <telerik:TextBoxSetting>
    <TargetControls><telerik:TargetInput ControlID="TextBox1" /></TargetControls>
    </telerik:TextBoxSetting>
    </telerik:RadInputManager>

[Dimo]

Hello Steve,

I see your point. Well, since the new behavior uses some Javascript to correct the width on the client (taking into consideration the padding and borders), and frankly we don't want to add this Javascript to the RadInputManager as well, we will introduce a property (in Q1 2009 SP1), which will determine whether the width should be corrected or not. The default value will be such, so that the previous behavior will be restored.

Kind regards,
Dimo
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.