-
Notifications
You must be signed in to change notification settings - Fork 46.9k
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
e.target.value
reflects <select value={}> not <option value={}> in Chrome on Windows 10
#5641
Comments
do you know what version of chrome this is? |
Your onChange handler is wrong Use this
|
That was just example code. It works fine on Mac and earlier versions of Windows. Latest version of Chrome. |
+1 I'm seeing this as well, but it doesn't reproduce in an isolated jsfiddle for me. Weird. |
Some more details. I was able to make the issue reproduce reliably by adding an
http://codepen.io/anon/pen/KVdzjR This reproduces in Chrome 47 on Windows and Linux, but not OS X, nor does it reproduce on Chrome 46 on any platform. |
I can confirm that I see the same behavior on Chrome 47 (on linux). My first selection (when initial value is null) works, and then subsequent selections fail to update the value. |
I found the same issue in latest Chrome 47. Is there any work around? |
Is this still an issue? |
I’ll assume this was a transient Chrome bug that was later fixed. |
I'm facing this issue on Safari 12. I'm receiving the selected option text instead of the selected option value, which is annoying. I'm using the code from the reactjs documentation. UpdateActually I had an |
Just a note, it works perfectly fine on earlier versions of Windows and Mac OS X
code:
Whenever the onChange is triggered, the
e.target.value
is 1. I'm assuming this is because that is the value starts with. And any changes do not correctly change the value.The text was updated successfully, but these errors were encountered: