fluentui
fluentui copied to clipboard
[Bug]: PeoplePicker - Cannot remove last item selection on Android devices
Library
React / v8 (@fluentui/react)
System Info
OS: Android 11.3
Device: Oneplus Nord2
Broswer: Chrome
Are you reporting Accessibility issue?
No response
Reproduction
https://developer.microsoft.com/en-us/fluentui#/controls/web/peoplepicker
Bug Description
Actual Behavior
Cannot remove last selection if the selected item is composed of two or more words (ex, First name + Last Name). Please refer to the attached video
Expected Behavior
It should be possible to remove the selection
https://user-images.githubusercontent.com/55849556/177868022-8018d95d-3b34-4e50-aaa7-dc2853c3441f.mp4
Logs
No response
Requested priority
Normal
Products/sites affected
No response
Are you willing to submit a PR to fix?
no
Validations
- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- [X] The provided reproduction is a minimal reproducible example of the bug.
@lutorre - Thanks for filing this issue with us. To set expectations the developers will review this issue once capacity allows.
@layershifter - I am not sure if this issue arose due to the fact we didn't cover android chrome versions in our support matrix? Would you be able to take a look and confirm - please. Thank you
I was able to reproduce this on my OnePlus with Android 11 on Chrome 104. This bug affects user experience, but we don't have mobile browser support for v0/v7/v8 in our browser support matrix, only v9 declares mobile support.
@JustSlone - we don't have mobile browser support for v0/v7/v8 in our browser support matrix, only v9 declares mobile support. Could you confirm the mobile support for the v0/v7/v8? is there any or not?
Yes, this bug is not a general Mobile issue, it only repros on specific browsers/OS. Also, if the selection is completed and the person is picked (resulting in the tag representation of the person) then the selection can be removed. So this lowers the impact of the issue.
We unfortunately won't be able to pickup fixing this particular issue anytime soon. We will make sure this gets resolved in future versions of library and this component, but we're not able to look at a fix specifically for v8.
If anyone wants to div in an investigate what is going on here and propose a minimal fix here, we would be happy to help review and merge the fix.
Because this issue has not had activity for over 180 days, we're automatically closing it for house-keeping purposes.
Still require assistance? Please, create a new issue with up-to date details.