RadNumericTextBox Numeric keypad decimal issue

[Karl]

Hi,

I am having an issue with the RadNumericTextBox. When I enter a decimal followed by a number using the numeric keyboard it swaps the value around. For example instead of being .5 it will be 5

 To emulate it what you need to do is

1. Copy the code below.

<telerik:RadNumericTextBox ID="ntxtMaxWorkHoursSitting" runat="server"
              Width="80px"
              CausesValidation="true"
              Type="Number" MinValue="0"
              MaxValue="24"
              ShowSpinButtons="true"
               IncrementSettings-Step="0.5">
                           <NumberFormat DecimalDigits="2" />
</telerik:RadNumericTextBox>

2. Run the website 
3. Enter some value into the RadNumericTextbox (e.g. 5) then click away and the value will turn into a decimal (e.g. 5.00)
4. Highlight the result (Just need to click back in there and it will highlight it for you)
5. Press the decimal key on the numeric keyboard (The decimal on the normal keyboard works fine) and then press 5

it should say .5 but instead it will change it to 5

Is there a fix to this or a way around this?

thanks in advance,

Karl

[Richard]

Karl,

I tried, unsuccessfully, to reproduce your reported behavior. Your provided markup works as expected with the decimal key on both the regular and the numeric keypads. I'm using the RadNumericTextBox 2012.1.411.40 and Mozilla 12.0 on a Windows 7 workstation.

Did you try this using a different workstation/keyboard?

Regards,

[Karl]

Hi jumpstart,

firstly, thank you for your help. I have just narrowed it down due to your suggestions. 

I am using Telerik Q3 2011. It works fine in Chrome but has the Issue in IE7-IE9.

I tried it on a machine with Telerik Q1 2012 and it is working fine in all browsers. Therefore it seems to be an issue with Q3 2011 with IE.

We can't do the upgrade to Q1 2012 at this stage. So is there any other suggestions? I could hack at the code but I would prefer a clean solution by Telerik.

Thanks

[Vasil]

Hi Karl,

The clean solution that you are looking for is to upgrade to the version in which this bug is fixed.

Regards,
Vasil
the Telerik team