Bug Report

Pressing the dot key on the NumPad does not apply the default decimal separator when the keyboard is set to EN-US/ UK. It always applies the dot. 

Steps for Reproduction

1. Set the culture to a culture that uses the comma as a decimal separator - Italian.
2. Switch the keyboard to EN-US/UK. 
3. Press the dot on the NumPad.
4. Validation prevents the input. 

Dojo sample for reproduction:

https://dojo.telerik.com/OXIsEVAk

Environment

jQuery version: 1.12.4

Kendo UI version: 2020.1.219

Browsers: [all]

Bug report

In case when culture is set to de-DE or nl-NL globally the NumericTextBox does not accept comma decimal separator from the Numeric keypad

Reproduction of the problem

Dojo: https://dojo.telerik.com/ARURAhOg

Current behavior
When comma from the Numeric keypad is pressed validation is fired.

Expected/desired behavior
Comma must be accepted as a decimal separator

Environment
**Kendo UI version: 2020.1.406

There is a limit in kendoNumericTextBox to 14 decimals. The request is to manage 15 or more decimals.

When users see a field where they're expected to enter a dollar amount, a lot of people intuitively try to type something like "$45.30".  However, since the shift key is forbidden, they get "445.30".  I suggest allowing users to type in a single, superfluous dollar sign as the first character in a CurrencyTextBox, and then ignoring it during form submit.

I know it's not officially supported, but when you use it in hybrid mode in an iOS UIWebView, the events sometimes seems to get mixed up. Then when you clic on a filed, it jumps to the the next one while flashing the keyboard. It doesn't happen always, but just clicking in a few fields on a form and it starts. We had to rollback using it in our codebase. I have a video of the behavior and the code (based on your mobile sample).

When I enter the following entry in  numeric text box
"1k" should populate "1000"
"1m" should populate "1000000"
"1g" should populate "1000000000"

For cases where validation after the fact isn't good enough there should be an option that disallows setting numeric textboxes to null. If the user sets it to null and moves to another field the textbox should reset to 0.

The Kendo UI NumericTextBox hides the decimal portion of its value when focus is in the control and when the decimal part is zero. For example a value of 1,345.00 will appear as 1345 when the focus is put in the control. If the decimal part is non-zero then the value is shown. From a usability viewpoint the disappearing zeros is inconsistent and can be misleading/confusing to a user who may not realize that they can enter a decimal part.

So I think it would be valuable for the control to always show the decimal part of the value.

It is better if kendo numeric textbox formats value (comma will be added after 3 decimals) as user types, especially for currency values.

There are so many jQuery plugins available in market to achieve this. Kendo Numeric text box is not working as expected when integrate with these plugins.

Demo url: https://www.jqueryscript.net/demo/Auto-Format-Currency-With-jQuery/

Please focus on adding flexibility to the numerictextbox. I'm jumping through hoops to get a field with a displayed percentage of 75.75% to appear the same way in edit mode. I understand the need to keep the control reasonably rigid, but I would hope additional customization options could be add. I gave up and am doing everything in a custom editor/ input text box.   

Add a popup calc like this one : http://keith-wood.name/calculator.html

When you use a NumericTextBox without attribute title, the widget creates automatically one with the current internal value, showing a annoying and unnecessary tooltip.

We would like remove this behavior or change it with a configuration item.

Something like:

<input id="currency" type="number" title="" />

$("#currency").kendoNumericTextBox({
    autoTooltip: false,
});

Provide an option for the Kendo UI NumericTextBox to select its value on focus.

This would be a useful feature for data entry situations so you can start typing immediately. 

We are aware of the proposed how to article but this is not a good solution for large applications. 

Can we have something like "selectOnFocus: true". The code fix for this could be:

When using the percentTextBox control, it would be nice if there was an option to have the control allow the editing of the data as a percent.  Currently it will show the percent as a decimal value (e.g. 50% would show .5)  For our users, it's more intuitive for them to enter the percent instead of the decimal value.  Kendo would need to do the conversion to/from percent and decimal behind the scenes so that the data is saved properly on the underlying model as a decimal value.

Currently AZERTY keyboards are not supported in NumericTextBox. In consequence:
1. It is not possible to enter a decimal separator in the control (because the key combination is "Shift + ;" - this can only be done using Caps Lock or the NumPad
2. It is possible to enter ; instead of the decimal separator
3. It is possible to enter the special symbols that are in the place of digits in QWERTY keyboards (again because digits are written using the Shift key).

The NumericTextBox currently has the ability to specify "decimals" - the number of decimal places allowed in the box. When a user types in a number with more decimal places than the box is configured for, the number gets rounded to the decimal precision.

What we'd like is to actually STOP the user from being able to type in more decimals than they're allowed. We don't want it to round; we want the user to just be disallowed from entering in a number that would be rounded.

Currently if k-min is set to 100 and a value less than 100 is entered the control will automatically change the value to 100.  

This is very poor behavior.  User input should NEVER be automatically changed to another value. The users rarely notice this and it leads to incorrect data being stored.

What should happen is that it should raise a validation error.  Further it should support using Angular validation for these errors.

I find it really confusing that when you hover over the kendo numeric textbox, the mouse turns 'disabled'.  the users i've worked with have no idea that they can click on the numerictextbox to change values inside.  Very not-intuitive.