Skip to content

Fix for empty <select> elements with value #3402

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

Merged
merged 1 commit into from
Mar 14, 2015

Conversation

vkramskikh
Copy link
Contributor

There is an exception when value or defaultValue is set but there are no
children as ReactDOMSelect tries to mark the first children as selected
even if there are no children.

Found this issue when upgraded to 0.13 from 0.12.

JSFiddle bug demo: http://jsfiddle.net/3tL0krav/

There is an exception when value or defaultValue is set but there are no
children as ReactDOMSelect tries to mark the first children as selected
even if there are no children.
@zpao zpao added this to the 0.13.1 milestone Mar 14, 2015
@zpao
Copy link
Member

zpao commented Mar 14, 2015

lgtm, thanks!

CC @syranide who broke (😉) this in #2241.

zpao added a commit that referenced this pull request Mar 14, 2015
Fix for empty <select> elements with value
@zpao zpao merged commit 68a2f89 into facebook:master Mar 14, 2015
@syranide
Copy link
Contributor

@zpao It seems your prayer wasn't heard ;) But yeah, my bad, I apparently forgot to consider the empty case.

zpao added a commit to zpao/react that referenced this pull request Mar 16, 2015
…th-value

Fix for empty <select> elements with value
(cherry picked from commit 68a2f89)
zpao added a commit that referenced this pull request Mar 16, 2015
Fix for empty <select> elements with value
(cherry picked from commit 68a2f89)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants