New issue
Advanced search Search tips

Issue 774420 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
pnangunoori@chromium.org
ligim...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Credentials are auto-populated in the fields even after deleting

Project Member Reported by pnangunoori@chromium.org, Oct 13 2017 
Chrome Version: 63.0.3238.0
OS: Windows 10, Cros, Mac 10.12.6 and Ubuntu 14.04

What steps will reproduce the problem?
1. Login to any website. Eg.: facebook
2. Enter login credentials 
3. Login and save the password.
4. Logout and navigatge to login page. (Notice the values of login credentials are auto-populates)
5. From the Omnibox, click on key icon.
6. Adjacent to the Password displayed, click on 'X' button to delete the saved password.
7. Observe that values which are auto-populated are not deleted.
8. Now click on "Login". User is able login because of populated Credentials.
9. Logout of the site.

Actual: Even after logging out of the website (page is refreshed), credentials are auto-populated in the fields.

Expected: As the page is refreshed, values should not be auto-populated.

10. Click on the Key displayed in the omnibox.
11. User can save the Credentials again (without entering the values after Step-6).
LoginCredentialsAutoPopulatedAfterDeleteing.webm
9.2 MB View Download

Comment 1 by pnangunoori@chromium.org, Oct 13 2017

Labels: OS-Mac

Comment 2 by battre@chromium.org, Oct 13 2017

Labels: -Pri-1 Pri-2

Comment 3 by kolos@chromium.org, Nov 3 2017

Labels: -Pri-2 Hotlist-Polish Pri-3
Owner: ----
Status: Available (was: Assigned)
After page reload, the deleted credential will be not available.
Project Member

Comment 4 by sheriffbot@chromium.org, Nov 5

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by vabr@chromium.org, Nov 6

Status: Available (was: Untriaged)
►

Sign in to add a comment