I would like to work on this

I think there is a workaround for this issue, according to the doc. Passing InputLabelProps={{ shrink: true }} as a prop to the TextField component will avoid this situation.

I see this isn't assigned to anyone? Can I give it a try?

I think there is a workaround for this issue, according to the doc. Passing InputLabelProps={{ shrink: true }} as a prop to the TextField component will avoid this situation.

This solves the issue...

Has this issue been resolved/closed yet? It seems like the problem has been solved @alisasanib . Unless there is something else that needs to be fixed.

Is anyone working on this? If not I will make the changes and create a PR

I think there is a workaround for this issue, according to the doc. Passing InputLabelProps={{ shrink: true }} as a prop to the TextField component will avoid this situation.

This solves the issue...

I don't think so. It is a good workaround though.

What if I have a form with multiple inputs? I would like them to have same look and feel. In case the form have a number or date input mixed with other text inputs, I would be forced to make all input labels to be shrunk.

I believe that issue should be properly resolved.

It seems that no one is working on that. I have made the changes and will work on the tests. Soon I will create a PR, if no one does first. :)

What is the location of the file which contains the sandbox code which needs to be edited in the repository?

@wladimirguerra is this still open I would like to work on this.

Is this issue still open? I would like to work on it.
I'm a first timer.
Could you put me through on the details so I could know what to do?

@adarshanand67 have a look at this draft to attempt to fix the problem. It seems to be simple but it is hard to make a proper test case because of the testing library limitation. I am not sure that the changes fixed the problem.

If this issue is still open can I give it a try ?

@prankurnov15 feel free to take it. It's not assigned to anyone.

Issue is with <input type="number" /> itself.
So In my opinion this can be solved by adding Regex check for type number

Is this issue still open ? I want to work on it

@kanishbodhwani do you have an idea of how you'd like to fix the problem? The number input has some inherent issues, and its behavior differs across browsers. There's a good article describing the problem: https://stackoverflow.blog/2022/09/15/why-the-number-input-is-the-worst-input/

@michaldudak Can I make a function that restricts user to input e in the text field, I've already tried in code sandbox, It worked for me. Please correct me if I am wrong

It's not just about "e". There are other characters ("+", "-", ".") that can make the input value invalid when misused. IMO recommending not to use type="number" would be the safest option.

There are not more, A single function can fix them all

I think this will work for chrome, not sure for other browsers.

Please review this

PS: I am not good in naming functions

As stated in the description of the issue and the article I linked, other browsers behave differently. In Firefox, for example, you can type any character. While I appreciate your efforts, I don't want to include a half-baked solution.

Additionally, your solution does not consider pasting a value in the input.

Okay, Thank you for the update. Will solve another issue :) 😊

Hi, can I try this one?