Bug - Number Input - Cannot clear value to specify a new value

[jgiardino]

Describe the problem
We are using a number input where we have a min value of 1. If the user wants to specify a value like 20, the user isn't able to easily clear the current value and specify a new value. E.g. inserting the cursor in the input and deleting the current value will result in resetting the value to the minimum value, i.e. 1. This is an odd user interaction and not consistent with how many users expect to specify values within an input.

How do you reproduce the problem?
Specify a minimum other than 0 in the PF example where min values are set. Place the cursor after the value in the input. Hit Delete. The min value still displays.

Expected behavior

• Allow the user to clear the value using the Delete key. This means that they will see no value displayed in the input.
• If the user leaves the input without typing a new value, then on blur, set the value to the min value of 1
• If the user specifies a value less than 1 in the input, then on blur, set the value to the min value of 1

Is this issue blocking you?
We currently have a bug open for this issue that was raised by QE. It is not considered critical. The workaround is to highlight the value and type the new value, but this isn't an interaction pattern that is common or obvious for users.

What is your product and what release date are you targeting?
Kafka

Any other information?