-
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 2022-10-04] [$250] Android - "Close account" button partially covers the text information when keypad opened #10903
Comments
Triggered auto assignment to @AndrewGable ( |
Triggered auto assignment to @michaelhaxhiu ( |
@michaelhaxhiu Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav ( |
Triggered auto assignment to @marcochavezf ( |
Note @mananjadhav -- we have a solution proposal above already, which was provided by @kakajann. Let's start there in terms of reviewing proposals. |
@marcochavezf @michaelhaxhiu I am fine with @kakajann's proposal if we're okay to reduce the height of the text input. But please note that this issue might still persist when we have smaller height devices. @kakajann Did you check if your proposal works on smaller devices like iPhone SE? |
Exactly. Thanks @kakajann. I think we should just focus on the second part of the issue. We can still reduce the number of lines so that it works fine for most devices (off lately all iOS devices from 8 onwards have a good large screen, excluding minis). Thoughts? @michaelhaxhiu @marcochavezf. Nevertheless, @kakajann's proposal is good for me. 🎀 👀 🎀 |
cc @Expensify/design for input on adjusting the text input to accomplish this change. Does that seem kosher? |
Hmm I think we had some open discussion about not making the bottom-docked button cover any of the content? Basically this conversation here. |
@shawnborton is this what we want here? Screen.Recording.2022-09-16.at.7.38.32.AM.mov |
That looks perfect, thanks! |
I've taken @shawnborton's comment here as a 🟢 to @kakajann's proposal and the fact that he has updated the proposals on feedback and raised the PR. |
Oh I forgot to assign @kakajann to the issue here, thanks for the proposal and the PR! |
📣 @kakajann You have been assigned to this job by @marcochavezf! |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.7-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2022-10-04. 🎊 |
@kakajann invited you to the job in upwork, can you accept when you have a chance? |
Just accepted |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
1 similar comment
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a production regression has occurred a Root Cause Analysis is required. Please follow the instructions here. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
@kakajann is paid. @mananjadhav please apply to this new job today (link) , since the OG job expired |
Everyones paid. 😎✌️ Keep it coming folks! |
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:
Actual Result:
The input fields and the button should not overlap and be too close to each other
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: v1.1.98-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:
https://user-images.githubusercontent.com/43996225/189174390-bcca3295-8cf3-4937-9835-68aa80bd9192.mp4
Upwork job URL: https://www.upwork.com/jobs/~015819339bfc73c40e
Issue reported by: Applause internal team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: