-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Hitting enter on an empty field selects the next contact #18598
Comments
Triggered auto assignment to @alexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
ProposalPlease re-state the problem that we are trying to solve in this issue.In workspace member invitation page, when we press the "Enter" key while the search field is empty, it will choose a contact and proceed to the following page. I'm not sure if this is intentional or not, but this is also happening on web and safari. What is the root cause of that problem?The current logic in BaseOptionSelector is selecting the default option, even when the text is empty. What changes do you think we should make in order to solve the problem?Adding a conditional statement in BaseOptionSelector to check if the text value is empty will solve the issue. + if (this.textInput.value !== '')
this.selectRow(focusedOption); Additionally, we should add a similar check for the What alternative solutions did you explore? (Optional)None RecordsWorking well after the fix working-android-18598.webm |
IMO this is not a bug as the first option is focused and it should get selected on Enter or Ctrl+Enter |
I'll try to test soon. |
I agree here that this isn't a bug. Thank you everyone here for participating. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
Hitting enter on an empty search field should not select any contact and proceed to the next page
Actual Result:
Hitting enter inside of an empty search field selects a contact and moves on to the next page
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.11.2
Reproducible in staging?: y
Reproducible in production?: new feature in invite members page
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Screen_Recording_20230507_161113_Chrome.mp4
az_recorder_20230508_134347.1.mp4
Expensify/Expensify Issue URL:
Issue reported by: @Nathan-Mulugeta
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1683465329596899
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: