-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
[$4000] iPad (safari) - Change password, new chat & new group page the field gets focused but the keyboard doesn't open - reported by @thesahindia #11089
Comments
Triggered auto assignment to @sonialiap ( |
I can replicate the behavior 👍 |
Triggered auto assignment to @MariaHCD ( |
Triggered auto assignment to @JmillsExpensify ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane ( |
Triggered auto assignment to @chiragsalian ( |
This comment was marked as off-topic.
This comment was marked as off-topic.
Also replicated the behavior. It's reproducible on Safari across all iOS platforms. I've created a job in Upwork here: https://www.upwork.com/jobs/~01f0a06e71a7da3f54. We're open for proposals! |
@JmillsExpensify Before closing, I think we should wait until Applause can't reproduce the bug in their weekly tests. (hold on doubling because i can't repro it either) |
Tested this not Reproducible. |
It's still reproducible for me. |
Woah, yes, I can reproduce this now. That said, I think this is a symptom of our larger keyboard issue and should be put on hold while we work through that initiative first. Tracking issue is here. Sound good? |
#10273 is related to KeyboardAvoidingView, as in how much the content should move up when the virtual keyboard is opened. This issue is about the keyboard not opening, so I think we should remove the hold. Thoughts? |
That's a good point. I was specifically thinking of this mention in the problem statement.
But I think you're right, being sluggish and opening slowly is different than not opening (on Ipad mWeb) at all. |
This comment was marked as off-topic.
This comment was marked as off-topic.
We're open for proposals again! |
Ohhh, I didn't know that and I see where you're coming from now. You might be right about holding this issue because a fix might involve using timeouts. |
Ah yes, all good! I like the idea of trying to verify one way or another via proposals. |
Doubling the price in the hopes of getting more proposals. |
Still waiting on proposals. I will circle back in the coming days to double the price if we still don't get proposals. |
Alrighty, doubling the price. When we get proposals, we'll be able to more accurately understand if this is related to the linked, and larger, keyboard initiative above. |
The proposal should be wholistic and fix the issue for all the following pages
|
Alright, doubling the price again. We still lack proposals. |
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:
Go to settings > security > change password
Expected Result:
The keyboard should open
Actual Result:
The keyboard doesn't open
Workaround:
unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.99-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
RPReplay_Final1661701238.mov
Expensify/Expensify Issue URL:
Issue reported by: @thesahindia
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1661709051676959
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: