[PIckerInput]: entered value clears when user put pointer in input repeatedly
Description (optional)
This issue is about disappearing entered value when repeated putting pointer in the input field.
Steps to Reproduce
- PickerInput with searchPosition='input' prop.
- Start typing anything
- After appearing values in dropdown put pointer back in the input
https://github.com/epam/UUI/assets/70166849/8bbb4d45-a2c5-4edf-9e03-167da7d6fb26
Actual result
Entered value cleared
Expected result
The entered text should stay unchanged. As is in PickerInput with searchPosition='body', so user can continue his search
Environment
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
- UUI version: latest
- Browser name: Chrome latest
- Operating System: Windows latest
Such behavior isn't related to the search typing, it's happening because we are clearing search value by picker close and in your case click in toggler of already opened Picker leads to its closing. I'm not sure that can do something with it, because both features - 'Toggle opened state by toggler click' and 'Clear search after dropdown close' is an a core ux requirements of this component. Probably we need to discuss, whether we need to close picker by click in toggler? @DzmitryTrubchyk what do you think?
As a one more solution, I will recommend to use searchPosition='body' for majority of cases, because this pattern more clear and not so confused according to the UX.
We've decided that we should not close body by click on toggler in case when searchPosition='input' and body is open now.
Please pay attention on case from this ticket.
https://github.com/epam/UUI/assets/57751283/1101dd1e-a553-470e-b45f-3d7a0254460f
[like] Dzmitry Trubchyk reacted to your message:
From: NatalliaAlieva @.> Sent: Monday, April 8, 2024 9:05:41 AM To: epam/UUI @.> Cc: Dzmitry Trubchyk @.>; Mention @.> Subject: Re: [epam/UUI] [PIckerInput]: entered value clears when user put pointer in input repeatedly (Issue #1822)
Please pay attention on case from thishttps://urldefense.com/v3/__https://github.com/epam/UUI/issues/2124__;!!GF_29dbcQIUBPA!3lnt3WywT66t6MImv9WdvbRmwyfeKxLvc_YUPadS7WpDbYhoi8AQM4x3-FVJt3el7qIQd4muZD2TKGpgOMeJUuaD1cQu0VQ$ ticket.
— Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/epam/UUI/issues/1822*issuecomment-2042237363__;Iw!!GF_29dbcQIUBPA!3lnt3WywT66t6MImv9WdvbRmwyfeKxLvc_YUPadS7WpDbYhoi8AQM4x3-FVJt3el7qIQd4muZD2TKGpgOMeJUuaDrabYtuI$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AKRKH6JGVP3VIIDRHWACMNTY4JMWLAVCNFSM6AAAAABAK4AFEKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBSGIZTOMZWGM__;!!GF_29dbcQIUBPA!3lnt3WywT66t6MImv9WdvbRmwyfeKxLvc_YUPadS7WpDbYhoi8AQM4x3-FVJt3el7qIQd4muZD2TKGpgOMeJUuaDfosj7CU$. You are receiving this because you were mentioned.Message ID: @.***>