Sign In - Keyboard shows up with form input helpers on mobile Chrome on the Sign In Page

[vincdargento]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Issue was found while executing QA for PR #55210

Version Number: 9.0.96-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: #55210
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: Samsung Galaxy A12 / Android 13
App Component: Other

Action Performed:

1. Navigate to staging.new.expensify.com
2. Tap on the "Phone or email" field

Expected Result:

The on screen keyboard shows up without any form input helpers (i.e. the key, credit card, and location options above the keyboard)

Actual Result:

The on screen keyboard shows up with form input helpers (i.e. the key, credit card, and location options above the keyboard)

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @joekaufmanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[SzymczakJ]

This is intentional, as I told in this comment, workaround that was merged in my PR won't solve the case when we have inputs that require some kind of inputMode to allow users to autocomplete(like passwords or emails).
So TextInputs like the one on SignIn page or the one on "invite to workspace" page will still have the input helpers and we haven't found any solution to this.
cc @yuwenmemon

[joekaufmanexpensify]

Got it, thanks for flagging @SzymczakJ! Caught up on that issue, and agree it sounds like this is intentional for now. Going to close for now, as it sounds like we already investigated this extensively and decided to do nothing.

LMK if any disagrees.