-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[HOLD for payment 2023-06-29] [$1000] Keyboard is popping up everytime user selects a contact when creating a new group #20636
Comments
Triggered auto assignment to @joekaufmanexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
ProposalPlease re-state the problem that we are trying to solve in this issue.We want to prevent the keyboard from opening up on every option selected in new group creation What is the root cause of that problem?We are passing What changes do you think we should make in order to solve the problem?We should remove <OptionsSelector
// shouldFocusOnSelectRow={this.props.isGroupChat} - remove this
// ... other code
/> The Alternatively, if we want to keep the focus on the input field on desktop web but not on mobile web, then we can only add shouldFocusOnSelectRow={this.props.isGroupChat && !Browser.isMobile()} What alternative solutions did you explore? (Optional)N/A |
Reproduced on Android mobile web. Also confirmed we don't do this on android native, or iOS native. I agree we should not open the keyboard every time a new contact is selected. 2023-06-13_14-34-48.mp4 |
Job added to Upwork: https://www.upwork.com/jobs/~0100b196cb7f4e7c43 |
Current assignee @joekaufmanexpensify is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel ( |
Triggered auto assignment to @marcaaron ( |
@huzaifa-99 you mean |
@marcaaron @huzaifa-99's proposal looks good to me. |
yes, thanks for spotting |
Thank you for the review |
I think we do. If that's the current behavior we should not change it. So that would be the alternate proposal in this case? @Santhosh-Sellavel you may have implied with your previous question that the alternative proposal is what we want - though, not sure. In the future, try make it clear whether you are recommending the main proposal or anything from the alternate proposal. Thank you 🙇 |
📣 @huzaifa-99 You have been assigned to this job by @marcaaron! |
Thanks for the feedback, yes keeping focusing on desktop and not on web would be the alternate proposal. Pr will be up soon |
@Santhosh-Sellavel @marcaaron PR up for review #20731 |
Based on my calculations, the pull request did not get merged within 3 working days of assignment. Please, check out my computations here:
On to the next one 🚀 |
@joekaufmanexpensify It got merged within 3 biz days. Melvin is confused here. |
@joekaufmanexpensify If you saw my conversations with @stephanieelliott you can see I have been reproducing the issue consistently and I have been providing a clear steps to reproduce the issue. There are 4 videos reproducing the issue perfectly on the closed GH. If you are convinced that the steps were not clear on the action performed section, it is alright. |
Accepted, Thank you! |
@joekaufmanexpensify I will get done with the checklist this week. Regarding payment I'm just waiting for the internal process, please check here |
Sounds good, thanks! |
@Santhosh-Sellavel we are all set to test your payment. Could you please complete your portion of the BZ checklist, and then I'll post new steps for payment in Slack. |
Pinged you on a Slack thread about payment. Caught up on other priority items, I'll complete the checklist this week in a day or two! |
Sounds good! As soon as the BZ checklist is complete, we'll issue the payments on this issue (besides yours, which is held for the new process). |
cc: @marcaaron Let me know if you differ on any of the above. What do you think about adding regression tests here? |
Regression Steps
👍 or 👎 |
I would rephrase this like:
But otherwise 👍 |
Hey guys payment has not been processed for this issue. @joekaufmanexpensify |
bump ^ |
Thanks! I was OOO the past two days, and previously we were waiting for the BZ checklist to be completed (which is required before we issue payments). I will finish this up and issue payment today. |
Added regressions test issue above. Only change I made is that I made step 1 specific to new group, rather than new chat as I think new chat was a typo (given this issue only applies when there is the ability to select multiple invitees). |
BZ checklist is now complete! All set to issue payment. |
@huzaifa-99 $1,500 sent and contract ended! |
@Nathan-Mulugeta $250 sent and contract ended! |
Upwork job closed. |
This one is all set, besides paying @Santhosh-Sellavel, which is on hold for the new payment process. |
@joekaufmanexpensify TYSM, also apologies I didn't knew you were OOO. |
Of course, and no worries at all! |
Still held on paying Santhosh |
Santhosh has been paid on New Dot |
Great, thanks! |
@Santhosh-Sellavel closing for now as payment has been issued. LMK if there are any issues receiving it! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
Keyboard should not popup every time user selects a new contact as this behavior is not seen on Android app
Actual Result:
Keyboard pops up every time user selects a new contact
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.26-3
Reproducible in staging?: y
Reproducible in production?: y
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_20230607_183004_Chrome.mp4
az_recorder_20230612_194921.1.mp4
Expensify/Expensify Issue URL:
Issue reported by: @Nathan-Mulugeta
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1686153010639509
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: