[data grid] Input type number lets type non number. about mui-x

[FreakDroid]

@michelengelen Thanks. how this is the expected behavior I'm going to close the issue.

[DanailH]

@FreakDroid can you check your reproduction link - it doesn't seem to work.

[FreakDroid]

@DanailH I updated the link. Sorry for that I missed it.

[michelengelen]

@FreakDroid this is not a bug with our implementation, but rather the behavior of the browser specific input implementation.

You can easily check that if you just render this:

export default function NumberInput() {
  return <input type="number" />;
}

in Chrome (chromium browsers) it prevents entering text, in Safari (webkit) it doesn't.

---

@cherniavskii do we plan on using the Number Input from Base UI in the future?

[FreakDroid]

@FreakDroid this is not a bug with our implementation, but rather the behavior of the browser specific input implementation.

You can easily check that if you just render this:

export default function NumberInput() {
  return <input type="number" />;
}

in Chrome (chromium browsers) it prevents entering text, in Safari (webkit) it doesn't.

@cherniavskii do we plan on using the Number Input from Base UI in the future?

@michelengelen thanks for your reply. Yes, I know about this issue but what I was thinking is that you said to use Number_input instead. Although this is not a blocker in our project, I will keep an eye on this topic.

[michelengelen]

@michelengelen thanks for your reply. Yes, I know about this issue but what I was thinking is that you said to use Number_input instead. Although this is not a blocker in our project, I will keep an eye on this topic.

@FreakDroid Thanks for your understanding. I am not sure, but my guess is that it was not available when building the filter panel. So what would be best from that point onwards is to open up a feature request to replace the <input type=""number /> with the NumberInput from baseUI.

I don't think that this is currently on our projects backlog.

[FreakDroid]

@michelengelen thanks for your reply. Yes, I know about this issue but what I was thinking is that you said to use Number_input instead. Although this is not a blocker in our project, I will keep an eye on this topic.

@FreakDroid Thanks for your understanding. I am not sure, but my guess is that it was not available when building the filter panel. So what would be best from that point onwards is to open up a feature request to replace the <input type=""number /> with the NumberInput from baseUI.

I don't think that this is currently on our projects backlog.

@michelengelen do you know if to do this I need to create a custom filter panel? Or if you have an example would be useful.

[michelengelen]

@FreakDroid you can use the filter panel customization. Here is an example on a custom input component.