-
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
[HOLD for payment 2024-05-22] [$250] Login - mweb - Login screen gets off center after selecting saved credentials #40559
Comments
Triggered auto assignment to @puneetlath ( |
@puneetlath FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors. |
This bug might be related to #vip-vsb |
Job added to Upwork: https://www.upwork.com/jobs/~01767f654b3e4ea3af |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @fedirjh ( |
@puneetlath, @fedirjh Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@kavimuru can you provide your android and chrome version? I tried to replicate it, but it didn't occur. Chrome 113 ![]() |
Are you able to repro @fedirjh? |
@puneetlath I can reproduce with these steps:
@kavimuru Can you test with these steps and see if you can reproduce the same issue? |
ProposalPlease re-state the problem that we are trying to solve in this issue.Login - mweb - Login screen gets off center when selecting all text content with dblclick What is the root cause of that problem?We are using an overflowHidden to wrap the SignInPageContent (The overflow: hidden CSS property on a parent component can clip any content that overflows its boundaries. This can affect how child components (like a TextInput) are displayed, especially when they extend beyond the parent's visible area due to text selection handles), when we select all the input content there is a moment where the magnfier (in android) try to adjust to the space available and we get the error / weird behavior. What changes do you think we should make in order to solve the problem?We can remove the overflowHidden for the rest of navigators/devices and let it in Safari when mobile (due the bug there is because the magnifier behavior) in the View component inside SignInPageLayout: Before changes: Before.changes.movAfter changes with previous bug fix tested: After.changes.-.mobile.safari.and.mobile.chrome.mp4 |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@charles-liang Your root cause analysis is not clear to me. It does not explain why this issue occurs when the input text is long. |
@samilabud It seems |
Hi @fedirjh, you were right, I have updated my proposal, I have included new video with evidence, here below what was happening with my previous proposal (was working for mobile chrome only): With.previous.proposal.-.mobile.safari.and.mobile.chrome.mp4 |
I understand that removing overflow: hidden might cause other issues, which is why I didn’t propose it. The longtext does not need to be very long; it only needs to exceed the length of the input box by a few characters, depending on the width of the whitespace to the right of the input box. On the other hand, position: fixed doesn’t expand the page and prevents scrolling. If this makes it clearer for you, I will update my proposal. |
@fedirjh how's this going? |
@charles-liang Thanks for the update. However, I am leaning toward @samilabud solution. I believe that removing the style causing the issue ( |
Let's proceed with @samilabud's Proposal. 🎀 👀 🎀 C+ reviewed |
Current assignee @puneetlath is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new. |
Sorry, just for my understanding, does Safari treat |
Not really, the problem with Safari is that it has a magnifying glass that affects the CSS and in this case makes the content move as if it had a scroll (even with the overflow hidden). |
📣 @fedirjh 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @samilabud 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.73-7 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 2024-05-22. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
BugZero Checklist:
Regression Test Proposal
|
Regression test update here: https://github.com/Expensify/Expensify/issues/398940 Everyone has been paid. Thanks y'all! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.63-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail: n/a
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:
precondition: user has at least 3 saved credentials
Go to https://staging.new.expensify.com/
Tap the email field
Dismiss saved password modal
Tap the email field again
Swipe the credentials and select the password icon
Scroll down and select the 3rd saved credential
Expected Result:
The login screen is fully visible
Actual Result:
The login screen gets off center and moves to the left
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6454281_1713475501494.video_2024-04-18_17-23-00.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @puneetlathThe text was updated successfully, but these errors were encountered: