Bug report

When selectOnFocus is enabled and the NumerictTextBox is focused programmatically, the value is not selected, but the cursor is set after the value.

Reproduction of the problem

1. Open the Dojo example - https://dojo.telerik.com/@NeliK/aWipeDit.
2. Click the button

Scenario 2:

1. In the Dojo above, click in the NumericTextBox and focus one of the digits, blur and click the button.

Current behavior

The value in the component will not be selected.

Note: If the user clicks on the NumericTextBox initially and then clicks the button, the value will be highlighted correctly.
In Scenario 2 the previous focus state will be displayed (a single digit will be highlighted).

Expected/desired behavior

The value in the NumericTextBox should be highlighted.

Environment

• Kendo UI version: 2024.3.806
• Browser: [all ]

setOptions() for numericTextboxes with restrict decimals set to true does not change the decimals setting. After clicking the Change Decimal button the display format correctly changes to 3 decimal places, but typing is still restricted to the original setting of 2.

 

Reproduction steps:

1) open the dojo https://dojo.telerik.com/uKECIxUv based on https://docs.telerik.com/kendo-ui/knowledge-base/numerictextbox-decimals-precision-runtime-change

2) (important) trigger the validation - e.g. try to type more decimals than the initial

3) Click the Change decimal button

Actual:

You can enter 2 decimals max

Expected:

You can enter 3 decimals max

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.

Bug report

Incorrect number when decreasing the value via the keyboard in MS Edge.


Reproduction of the problem:

1. Open a NumericTextBox demo in the Edge browser. 
2. Focus on input. 
3. Increase the value to 3 using keyboard arrows. 
4. Press the Tab button so NumericTextBox loses focus. 
5. Press Shift+Tab buttons to bring the focus back to the NumericTextBox. 
6. Decrease the value using the keyboard arrow.
7. Value is decreased by two, while it should be decreased by one.
 

Current behavior:

When decreasing by the keyboard arrow, the value of the NumericTextBox goes directly from 3 to 1.

 

Expected/desired behavior:

When decreasing by the keyboard arrow, the value of the NumericTextBox should be decreased by one without skipping values.

 

Environment:

* **Kendo UI version:** 2020.2.513
* **jQuery version:** 1.12.4
* **Browser:** Microsoft Edge 44.18362.1.0

### Bug report

When the Kendo UI NumericTextBox has the factor property set and a value pasted, a wrong number is output.

### Reproduction of the problem

1. Create a NumericTextBox and set the format and factor properties.

2. Set a value. Copy and paste value greater than 1.

3. The value 100 is applied to the widget.

Dojo sample for reproduction:

https://dojo.telerik.com/ufOSEGEn

### Expected/desired behavior

The pasted value should be applied to the widget.

### Environment

* **Kendo UI version:** 2021.1.224
* **jQuery version:** 1.12.4
* **Browser:** [all]

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.

Bug report
Since R1 2022 spin event is no longer triggered when setOptions is called in NumericTextBox

Reproduction of the problem
Dojo: https://dojo.telerik.com/eTAfAyuP

Expected/desired behavior
Spin event shall fire after setOptions() is called.

Environment
Kendo UI version: 2022.1.119 or above
jQuery version: All
Browser: All

When calling setOptions on the numericTextBox, the spinner locks up if there is a "factor" option set. 

https://dojo.telerik.com/OYiYogis 

See the above Dojo.

Removing the factor seems to fix the issue, but I need the factor so that a user can type in 10 for 10% when the type is percentage but 10 for $10.00 when the type is currency.

got a pretty simple one here.  Your page explaining decimals has bad info on it.
https://docs.telerik.com/kendo-ui/api/javascript/ui/numerictextbox/configuration/decimals

It claims that when you are accepting two decimals, entering 12.99 will get rounded to 13.00.  this doesn't happen and would be wrong if it did.

### Bug report

NumericTextBox cannot be initialized when element with id options is present on the page. For instance, a div element with id="options".

### Reproduction of the problem

1. Create a NumericTextBox.
2. Add an element with id options.

Dojo sample for reproduction:

https://dojo.telerik.com/oWIwUSAp

### TicketID: 1562966

### Environment

* **Kendo UI version:** 202x.r.ddd
* **jQuery version:** x.y
* **Browser:** [all]

Bug report
The pasted value containing whitespaces into numeric textbox results in a trimmed value

Reproduction of the problem

Open this example: https://dojo.telerik.com/iTiBArEh

Click "Run"

Paste "1 000" into the NumericTextBox

Expected/desired behavior

The pasted value shall be '1000' instead of '1'

Environment
Kendo UI version: 2021.2.616 and above
Browser: [all]

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

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.

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.

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.