App
App copied to clipboard
[$250] mWeb/Safari - Log in - The cursor does not focus on the password input field
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:
1.Go to https://staging.new.expensify.com/ 2. Enter the email on the email field 3. Click continue
Expected Result:
The cursor should be focus on the password section
Actual Result:
The cursor does not focus on the password input field
Workaround:
Unknown
Platform:
Where is this issue occurring?
- Mobile Web/Safari
Version Number: 1.2.26.0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/201133721-a89de99f-7fd5-4138-a6a0-753b15bc0703.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Triggered auto assignment to @arielgreen (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details.
Current assignee @arielgreen is eligible for the External assigner, not assigning anyone new.
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane (External
)
Triggered auto assignment to @techievivek (External
), see https://stackoverflow.com/c/expensify/questions/7972 for more details.
https://www.upwork.com/jobs/~016a5c80040608f342
I think this has the same root cause as https://github.com/Expensify/App/issues/10414
My plan is to ensue the dispatch action target is set properly in Navigation.js. (151: navigationRef.current.dispatch(StackActions.pop()) looks like it may need a conditional. If not, I'll debug further in DrawerAction.js, BrowserAction.js, or there imports. @arielgreen, I can have an update in 3 days. Let me know if you need anything else before I commence.
Looks like something related to react-navigation
may have been mentioned in this issue discussion.
As a reminder, please make sure that all proposals are not workarounds and that any and all attempt to fix the issue holistically have been made before proceeding with a solution. Proposals to change our DeprecatedCustomActions.js
files should not be accepted.
Feel free to drop a note in #expensify-open-source with any questions.
Aaah yes, we don't need to look into this one because we are deprecating it.