Skip to content
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

Web - Settings - Pressing tab on password field won't go straight to next one #6618

Closed
kavimuru opened this issue Dec 7, 2021 · 6 comments
Closed
Assignees
Labels
DeployBlockerCash This issue or pull request should block deployment Engineering Hourly KSv2

Comments

@kavimuru
Copy link

kavimuru commented Dec 7, 2021

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Issue was found when executing the PR #6501

Action Performed:

  1. Open app and login
  2. Go to profile > change password
  3. Click on first field and type pass
  4. Press Tab key

Expected Result:

User is brought to the next fillable field

Actual Result:

After pressing tab, focus goes to new hide/show password icon.

Workaround:

Unknown

Platform:

Where is this issue occurring?

  • Web

Version Number: 1.1.18.0
Reproducible in staging?: Yes
Reproducible in production?: No
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Issue was found when executing the PR #6501

Bug5362473_Untitled_82.mp4

Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:

View all open jobs on GitHub

@kavimuru kavimuru added the DeployBlockerCash This issue or pull request should block deployment label Dec 7, 2021
@OSBotify
Copy link
Contributor

OSBotify commented Dec 7, 2021

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

  1. Identify the pull request that introduced this issue and revert it.
  2. Find someone who can quickly fix the issue.
  3. Fix the issue yourself.

@MelvinBot
Copy link

Triggered auto assignment to @NikkiWines (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@parasharrajat
Copy link
Member

This is the technically correct flow for tab navigation so this is not an issue.

@isagoico
Copy link

isagoico commented Dec 7, 2021

@anthony-hull I agree with @parasharrajat here - I think this is the expected behaviour now with the new Visibility toggle - can you confirm so we can close this issue 😬 Thanks in advance

@anthony-hull
Copy link
Contributor

I agree it should go to the visibility toggle before the next field.
We shouldn't make the toggle unreachable in keyboard navigation and putting it in another position in the tab index would negatively affect the context for the control to the input.

@NikkiWines
Copy link
Contributor

Cool, sounds like this is a non-issue, closing as this is not a deploy blocker.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DeployBlockerCash This issue or pull request should block deployment Engineering Hourly KSv2
Projects
None yet
Development

No branches or pull requests

7 participants