-
Notifications
You must be signed in to change notification settings - Fork 47k
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
Correctly select options when nested inside an optgroup #6442
Merged
Merged
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next
Next commit
Correctly select options when nested inside an optgroup
- Loading branch information
commit b102e256634ce7973eee6695e9aa8cb46ad14e42
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -537,4 +537,22 @@ describe('ReactDOMSelect', function() { | |
"Cannot set property 'pendingUpdate' of null" | ||
); | ||
}); | ||
|
||
it('should select grandchild options nested inside an optgroup', function() { | ||
var stub = | ||
<select value="b" onChange={noop}> | ||
<optgroup label="group"> | ||
<option value="a">a</option> | ||
<option value="b">b</option> | ||
<option value="c">c</option> | ||
</optgroup> | ||
</select>; | ||
var container = document.createElement('div'); | ||
stub = ReactDOM.render(stub, container); | ||
var node = ReactDOM.findDOMNode(stub); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You don't need to do a findDOMNode here. The value returned by render is the node, so |
||
|
||
expect(node.options[0].selected).toBe(false); // a | ||
expect(node.options[1].selected).toBe(true); // b | ||
expect(node.options[2].selected).toBe(false); // c | ||
}); | ||
}); |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need a null check here, because selectParent could be null at this point, right?