New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 825690 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Feature



Sign in to add a comment

Add "eyeball" icon so the user can check which password the browser intends to help him enter

Reported by jidanni@gmail.com, Mar 26 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.22 Safari/537.36

Steps to reproduce the problem:
Here we see the browser is asking us if we want to use the password for
our email address.

That would be great. However the user wishes to double check which
password the browser intends to help him fill in.

Yes he can count the dots that get filled in, but that still leaves him
worried.

As you know, assuming the browser has filled in password A only to later
find out it was password B or who know which of his many passwords,
might likely lead him to later be locked out of what he submitted now.

Because there is no "eyeball" icon there where he can do a quick check
as to which password is meant, he dares not accept, and ends up filling
the password in by hand in the end anyway.

Yes you might argue that he can at any time check all the passwords in
Settings.

However the user does not want to spends five minutes poking around
Settings looking for it. By the time he is finished he might have messed
up the form he was almost finished filling anyway, who knows.

What is the expected behavior?

What went wrong?
Without confidence in which password will get filled in, nobody will dare allow it to fill it in for them...

Did this work before? N/A 

Chrome version: 66.0.3359.22  Channel: n/a
OS Version: 
Flash Version:
 
Labels: Needs-Triage-M66
Cc: sindhu.chelamcherla@chromium.org
Components: -UI UI>Browser>Passwords
Labels: -Type-Bug Triaged-ET M-67 Target-67 FoundIn-67 OS-Mac OS-Windows Type-Feature
Status: Untriaged (was: Unconfirmed)
As per comment#0 this seems to be a feature request. Hence marking as Untriaged.

Thanks!

Comment 3 by vabr@chromium.org, Apr 3 2018

Cc: nepper@chromium.org battre@chromium.org
Labels: -Pri-2 -M-67 -Target-67 -Needs-Triage-M66 OS-Chrome Pri-3
nepper@ and battre@, is this something which fits our "Beyond the basics" part of the roadmap?

Comment 4 by vabr@chromium.org, Apr 17 2018

Owner: nepper@chromium.org
Status: Assigned (was: Untriaged)
Hi nepper@, what is the process for discussing feature requests on the team?

Sign in to add a comment