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

[GlobalStep] The wrong icon is used when a Password is visible #11307

Closed
wptester9845 opened this issue Feb 14, 2020 · 3 comments · Fixed by #11983 or wordpress-mobile/WordPress-Login-Flow-Android#38
Assignees

Comments

@wptester9845
Copy link

Description

While when a Password is hidden the icon of an eye with a slash is displayed, when the user presses that button so the Password becomes visible the icon shown is the WordPress icon but the same eye without the slash should be displayed.
Besides the devices mentioned below, this issue was also tested on the LG G3 (5.0) but not seen to occur on this device.

Reproduction Rate

4/4 100%

Expected behavior

The eye icon should be displayed.

Actual behavior

The WordPress icon is displayed.

Steps to reproduce the behavior

  1. Install WordPress 14.2
  2. Press the Log In button.
  3. Type in a valid email address.
  4. Select the “Enter your password instead” option.
  5. Press the Eye button to make the password visible.
Tested on the following

Samsung Galaxy J3 (8.0.0)
Samsung Galaxy Tab S2 8.0" (7.0)

Please see the attached screenshot for more information

Submitted by:

Luis Pimenta

@rachelmcr
Copy link
Member

I confirmed this also isn't an issue on my moto e5 play — I'm guessing it's Samsung-specific.

@marecar3 I see you worked recently (in #11172) on the password visibility icon. Could you take a quick look and see if any ideas come to mind as to why this would happen?

@marecar3
Copy link
Contributor

Hey @rachelmcr,

Thanks for the update. This is very important feedback for us.
I will reference it in the main issue.

@marecar3
Copy link
Contributor

Hey @rachelmcr @designsimply with a bit of luck I have found the root cause of this problem.
Here is the fix: #11983

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants