The NumericTextBox should behave like standard input fields and automatically select all the text when tabbing into the control. This should work for NumericTextBox controls whether using inside or outside of a Kendo grid.

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.

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.

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 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).

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.

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.