Issue with Input component

[namuller]

Hi!
Not sure if this is a bug or an issue on my personal use case:
When I use Input component and set type = number and min = 1 then the first value I set has those constraints but after deleting that value I can type in whichever value under 1. Can this min and max constraint only be set for the arrows which can help to set the value and not for typing the value in the input?

[TwilioPasteBot]

Disclaimer: This is a very experimental bot using OpenAI's GPT-4. The answers may not be correct, a human will review the answer and update it if necessary.

---

The Paste documentation does not explicitly mention whether the min and max constraints apply only to the arrow keys or also to the typed input when using the Input component with type="number". However, it does suggest using Help Text to explain what inputs are accepted, like minimum or maximum values. This could be a way to guide users about the acceptable input range.

Here's an example of how you might use Help Text with your Input:

<Input type="number" min="1" />
<HelpText>
  Please enter a number greater than or equal to 1.
</HelpText>

If you're still experiencing issues, it might be a good idea to check with the developers or the community for more specific guidance.

I also did a search, and I managed to find these other Discussions that might be similar or related to your question. Give them a read to see if they answer your question. If they do, head back here and update this discussion and mark it as answered, pointing others to the related discussion:

• Input type=number data validation (updated: 07/06/2022, similarity score: 85%)
• Input type=number data validation - Answer (updated: 07/06/2022, similarity score: 85%)
• Input type="number" (updated: 06/28/2022, similarity score: 83%)

[SiTaggart]

Hi @namuller

Would it be possible for you to create a reproduction for us to see exactly what you're doing and what you're seeing? That'll help us get on the same page and start looking into your issue for you.

Something like Codesandbox would be ideal.

Thanks

[namuller]

Hi @SiTaggart , thank you for the reply. Here is: Example in Codesandbox

[SiTaggart]

Hi @namuller

I don't think this is a bug, it's behaving how I would expect and how the HTML input[type="number"] works. The constraint is placed on the input, and the nudging controls are explicitly tied to that input and its constraints.

I acknowledge that it is annoying that in some browsers I can enter values that don't meet the constraints set on the element itself. In Chrome for example I can type 0, but not a letter. In Safari I can type a letter or 0. That is just how the HTML element works in those browsers right now.

[namuller]

Understandable, thanks a lot for taking a look and getting back to me, @SiTaggart !