[$500] mWeb/Safari - Profile - Cursor not displayed in country field on tapping country option in address form

[lanitochka17]

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.6-2
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
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

1. Navigate to staging.new.expensify.com & log in
2. Tap settings icon in LHN
3. Select Profile >> Personal details
4. Tap Address option
5. Tap on Country option

Expected Result:

Cursor should be displayed in country field to highlight the field is focused

Actual Result:

Cursor not displayed in country field on tapping country option in address form

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6296237_1701363086710.DJAS9085.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01208951412ab720ab
• Upwork Job ID: 1730285832120459264
• Last Price Increase: 2023-12-07

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01208951412ab720ab

[melvin-bot]

Triggered auto assignment to @puneetlath (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane (External)

[AmjedNazzal]

I can't reproduce this, tried on iOS 16, iOS 17 and the newest web safari and I can't reproduce this on staging at all

[melvin-bot]

@puneetlath, @sobitneupane Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

@puneetlath, @sobitneupane Huh... This is 4 days overdue. Who can take care of this?

[puneetlath]

@sobitneupane are you able to reproduce?

[sobitneupane]

I can reproduce the issue. It is reproducible for all the text inputs (single inputs) that are supposed to autofocus after the screen navigation. I believe those issues are quite old and were reported many times.

[sobitneupane]

#26312 is a similar issue. This is the list of similar issue.

Some of those issues were closed with this reasoning.

I couldn't reproduce this on the emulator, but it's reproducible on a physical device. This is a browser limitation for mobile Safari. Apple blocks any programmatic focus that was not invoked in response to a user gesture.

Not sure if there is anything that we can do here.

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[melvin-bot]

@puneetlath, @sobitneupane Huh... This is 4 days overdue. Who can take care of this?

[puneetlath]

Ok let's close it for the same reason as that issue then. Thanks @sobitneupane