Clearing history (passwords) deletes passwords on passwords.google.com |
|||||
Issue descriptionVersion: M55 OS: All, try below steps on any platform as long as sync is enabled What steps will reproduce the problem? (1) Go to chrome://history (2) Click on clear browsing data (3) Select passwords and click 'clear browsing data' What is the expected output? Passwords on passwords.google.com dont delete If thats the case, please show a warning that says so What do you see instead? All my passwords are gone from passwords.google.com maybe because it is in sync with Chrome. Its an expensive realization which continues to promote need for 3rd party password managers.
,
Oct 10 2016
,
Oct 10 2016
+battre/zea This is WAI. passwords.google.com exposes the passwords stored in Google's password manager, which is synced with your passwords stored in Chrome (via Chrome Sync). If you delete your passwords in Chrome, they get deleted from the server as well. Sabine, re-assigning to you to consider the feature request to display a notice when clearing passwords as part of the CBD dialogue flow.
,
Oct 13 2016
+msramek, maxwalker who work on the CBS dialog.
,
Oct 13 2016
This is indeed WAI - p.g.c. and Chrome browser are just two different clients of the same synced passwords storage, and both clients offer the option to clear it.
Currently, we have a warning about synced deletion in the footer ("Synced data will be deleted from all devices"), although admittedly p.g.c. is not really a 'device'.
There is issue 565216 filed to show for each datatype whether it is synced or not. We could address the suggestions in there. Though my preference would be to show some kind of icon next to each checkbox to indicate whether it is synced.
In the long term, we plan to redesign the dialog so that 'passwords' will probably end up somewhat hidden to prevent people from shooting themselves in the foot, but that will take time.
,
Oct 21 2016
#5 gives a sufficient explanation, bug 565216 is a nice action item to help users in this area, there is no more actions to take on this bug. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by jainabhi...@chromium.org
, Oct 10 2016