-
Notifications
You must be signed in to change notification settings - Fork 389
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
[BUG] PeoplePicker won't accept Multiple Users with the same name #1612
Comments
Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible. |
Thank you for submitting your first issue to this project. |
Hi @sionjlewis I tried to reproduce the issue with and i guess i have found the fix. Will soon create a PR on this. Thanks, |
Brilliant, thank you @NishkalankBezawada |
Closing as fixed in version 3.16.0 |
Bug Description
When we attempted to add multiple users with the same name (Charlotte Coker was out test for this as there are 3 different users set up with her name) it fails to surface any user after the first when you search:
When we search the user (Charlotte) initially all three user accounts display in the search result but after selecting one and starting to search for the second no more return (as screenshotted)
To Reproduce
Steps to reproduce the behaviour:
<PeoplePicker
context={this.props.context}
titleText="People Picker"
personSelectionLimit={200}
showtooltip={true}
onChange={this._getPeoplePickerItems}
showHiddenInUI={false}
principalTypes={[PrincipalType.User, PrincipalType.SharePointGroup, PrincipalType.SecurityGroup]}
resolveDelay={1000} />
Expected behavior
I would like to see two or more John Smiths added to the field and replicate the SharePoint out-of-the-box people picker UX.
Suggested Fix
I understand that displaying three [John Smiths] [John Smiths] [John Smiths] will introduce another issue. Which [John Smiths] am I looking at. I currently see two options:
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: