Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Number Input with defaultValue does not accept decimal input #8211

Closed
dphaener opened this issue Nov 5, 2016 · 5 comments
Closed

Number Input with defaultValue does not accept decimal input #8211

dphaener opened this issue Nov 5, 2016 · 5 comments

Comments

@dphaener
Copy link

dphaener commented Nov 5, 2016

Do you want to request a feature or report a bug?
Report a bug

What is the current behavior?
When using a number input that has a defaultValue, you cannot enter a decimal value. When attempting to type a decimal, the cursor is moved to the beginning of the input. This behavior is not observed when there is no defaultValue given.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/reactjs/69z2wepo/).
https://jsfiddle.net/zc0x3egz/

What is the expected behavior?
The input should allow you to type a decimal.

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
This is happening with React 15.3.2. It does not happen in 0.14.x

@nhunzaker
Copy link
Contributor

Hey! I fixed this with #7750. However it looks like it hasn't made its way to a release yet.

@aweary
Copy link
Contributor

aweary commented Nov 5, 2016

#7750 is not included in the 15.4.0 release as far as I can tell. At this point it might be too late to include it since the RCs have been out for a while, and #7750 is a change that we'd likely want tested in RCs before releasing.

@nhunzaker
Copy link
Contributor

Totally understandable. Please let me know if I can help in any way.

@aweary
Copy link
Contributor

aweary commented Nov 5, 2016

I think @gaearon is managing releases now? Not sure with all the recent roster changes 😄

Going to close this out as well, since it's essentially a duplicate of #7253 and a fix is already merged into master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants
@nhunzaker @dphaener @aweary and others